Introducing SocialGPT

Posted on by

SocialGPT is a lightweight but powerful Chrome extension that integrates ChatGPT directly into your social media experience. For years, I’ve wanted a tool that would let me write smarter, sharper, more context-aware replies without opening new tabs or juggling windows. Every time I needed to draft a rebuttal or clarify a point, I wished for something embedded – something right there on the page.

Now it exists.

With SocialGPT, you can mark comment threads, automatically pull their content into an in-page editor panel, and generate AI-assisted replies in seconds – no reloads, no switching, no bullshit.

Source code: Bitbucket – GitHub mirror

Key Features

  • Context Marking – Highlight any number of elements in a thread to build a structured conversation context with block indexes (like [1], [2], etc).
  • Floating Reply Panel – A modal-less in-page editor where you can:
    • choose tone (e.g. cynical, friendly, brutally honest)
    • select response length (short, micro, extended)
    • switch models (GPT-4o, GPT-4, o3-mini)
    • input modifiers and custom instructions
  • Facebook-Aware – Automatically detects your profile name and injects it into the prompt for authentic replies.
  • Right-Click Access – Mark content or open the reply interface with a right-click.
  • Mark Mode Toggle – One-click switch to enable or disable GPT reading mode.
  • Response Modification – Use the Modify button to rework or fine-tune previous replies with new tone, instructions or shortened versions. This is especially useful after generation, since context and prompt fields are cleared upon reply.
  • Visual Loader – Subtle spinning loader shows when ChatGPT is generating content.
  • Fact Check Reminder – Prompts include reminders to validate and cross-reference controversial claims or disputed data before producing a final draft. Designed to prevent regurgitation of unchecked social media noise.

Tone Profiles

Organized into four categories:

  • Objective & Informative – neutral and formal, fact-based and concise, academic and precise, analytical and critical
  • Confrontational & Direct – critical and direct, cynical and sharp, aggressive and unapologetic, brutally honest
  • Satirical & Sarcastic – sarcastic and dry, snarky and dismissive, satirical and ironic, witty and clever
  • Approachable & Light – friendly and casual, conversational and soft

Ideal Use Cases

  • Rebuttals in comment sections
  • High-speed debate replies
  • Satirical or snarky thread injections
  • Public moderation with edge
  • Clarifying academic-style posts

Requirements

  • OpenAI API key (GPT-4 or GPT-4o recommended)
  • Chrome browser with extensions enabled

Created by Thomas Tornevall for real-world online interaction. Feedback and pull requests are welcome at either GitHub or Bitbucket.

Stay sharp – speak smart – strike fast.

Tornevall Networks changing some structure just slightly – The birth of Sonic Syndicate

Posted on by

We are still here! But there have been quite a few changes recently, both major and minor. NetCurl, which has long been a key feature of this website (frequently highlighted), reached its peak with the release of version 6.1, which introduced a range of improvements and functional updates. Earlier versions like 6.0.26 played some role, but the main focus was on refining and stabilizing the 6.1 series framework due to 6.0’s structurally poor and non-PSR-compliant foundation. The underlying TorneLIB framework was particularly affected, resulting in a chaotic structure.

In terms of marketing, NetCurl was never particularly prominent, despite being introduced via network components in certain Resurs Bank plugins (notably in version 1 of the ecomphp project, which initially required support for both SOAP and REST). That project also transitioned to a REST-only approach. Development of ECom2 began in early May 2022, rendering NetCurl largely obsolete. ECom2 includes its own integration inspired by NetCurl but designed to operate without external dependencies.

As stated: what was relevant then may no longer be. NetCurl’s domain has been relinquished and the project is no longer actively developed. The most active phase occurred in October 2021, followed by another 20 or so commits through spring 2022, during the era of PHP 7.x. On March 27, 2025, the commit message “netcurl is dead, fraudbl is new” appeared-intended as a nod to the preexisting fraudbl rather than indicating a shift. No further development is planned. However, NetCurl remains available as an LTS-based product and is still occasionally maintained, especially in connection with ecomphp.

Why the shift? Life circumstances evolve, and time for personal projects must be reevaluated. NetCurl was created during a time of ample free time. Today, the focus has shifted, and while development continues, it happens on a smaller scale. In addition, more energy is now being directed toward music (Thomas Tornevall’s second hobby), limiting the ability to maintain codebases as before.

But enough about that!

The platform “Sonic Syndicate” (https://artists.tornevall.net/) has been launched to support artists in need of a website presence. It is especially useful for streamlining the Spotify artist verification process.

And what about everything else? Well, most services are still running just fine. Tornevall Networks’ DNSBL is not currently under active development, as it remains functionally valid and stable. There are no plans to decommission it, and the fraudbl project continues in parallel. Mail services are fully operational, and there’s no intention to discontinue them. Since these systems are stable, they’re here to stay. The website will likely see further updates in the future – perhaps even more regularly, given the growing involvement in the music scene.

Preparing for netcurl 6.1.5

Posted on by

We’ve been holding on netcurl 6.1.5 for a while now, since the package has been a bit too small to be considered release worthy. However, the last days changed this and two bigger features has now been fixed: SoapClient timeouts and the ability to disable SSL certificate verification (which has been planned for long now).

SSL Verification becomes configurable

The verification issues is added as part to the fact that requests to self signed sites sometimes is necessary and normally netcurl security is set to never allow self signed or invalid SSL certificates. This release also contains a fix that makes the streamwrapper handle errors better, since we need to be able to catch SSL request exceptions.

SoapClient Timeouts

The SoapClient timeout handler has just recently become a problem. When a site is timing out during connection or the response, the SoapWrapper (and actuallty SoapClient itself) have never been able to figure out if exceptions thrown are thrown because of site errors or timeouts – except for through the error message.

With the new fix, a different exception will be produced under very specific circumstances: If the SoapClient throws an exception, based on error code 2 (E_WARNING), and the initial request time has exceeded the timeout configuration (from WrapperConfig) the exception is considered timeout instead of code 2. In such cases, the exception will be rethrown with code 1015 instead – but keep the error message produced by during the soap request.

const LIB_NETCURL_SOAP_TIMEOUT = 1015;

A major update for DOM Documents

DOMDocuments has always been of interest for netcurl, especially since we use those features to fetch data for RSS feeds. The most recent fixes to handle DOM data with netcurl will now become available. However, there may be a continued integration with Laminas here to furthermore make requests more stable.

Below, you can see what’s been updated.

    Release Notes - PHP_NETCURL - Version 6.1.5
  • [NETCURL-338] – Docblock classes are not properly defined
  • [NETCURL-330] – Allow manipulation of SSL Verification settings
  • [NETCURL-335] – PHP 8.1 Tests
  • [NETCURL-339] – Use xpath to fetch rendered elements
  • [NETCURL-340] – xpath automation of the otherwise manual handling
  • [NETCURL-341] – Separate DOMHandler from GenericParser
  • [NETCURL-343] – Try to verify soap timeouts.
  • [NETCURL-345] – Remove SSL verification configuration for older PHP

RSS Feed is no longer in beta state

Posted on by

Documentation about the /rss resource can now be found here!

Tornevall Networks has, for a while now, been running a RSS feed agent in a kind of beta mode. This period has been used to safely make sure that the services are really properly running, fetching data and provides the data correct in the feed. So far, the flaws has been very few so it is considered no longer a beta testing.

We are also monitoring RSS-feeds, which may seem a bit contra productive. However, there are purposes for this too. Amongst a few, this makes it possible for us to get a compiled view of multiple sites that handles the same kind of categories. For example, if you have several RSS-feeds for Marvel content, this makes it also possible to merge those feeds into one.

Furthermore, we are also monitoring sites where there are no RSS-feeds available. You can read about the feeder above, at the first link. We also keep track of the total feed agents helping collecting data and the status at https://auth.tornevall.net/portal/.

To get a full list of RSS feeds currently available, you can read it in json, instantly from the url below. If you want to add a new feed to this monitor feel free to contact us via the page Contact.

https://tools.tornevall.net/api/rss

DNSBL – tornevall.org – DNS Update: Moving resolvers

Posted on by

All secondary DNS servers for tornevall.org is currently being updated. Secondary services will from now on be hosted via Linode. As we are dismounting some internal DNS servers, this is one step in that progress. A second purpose of this change is also to make resolving faster worldwide.

The primary DNS, which is also currently the one that handles listings/delistings will be moved into a multi-address server, which means there are at least three entry points to it.

Changes amongst our DNS services, our beloved Stockholm Service shuts down in the end of 2023

Posted on by

The service that ns1.tornevall.net relies in runs an older version of OpenVZ which will reach an end of support 2023-12-31. Therefore, we will prepare to transfer this service elsewhere, probably already during this summer. If your DNS services depends on this, make sure you’re no longer using it.

The work has recently also started to migrate to a new master DNS. This work was finished today, which means that the API (v3) as of today communicates with a DNS that has closer reachability.

Taking a step forward

Posted on by

It has been a while since we touched api’s but this weeken we took a small step forward to replace an old API package. Instead of staying in a sphere of self maintained system, we’re about to try to run entirely over a Lumen instance. One of many reasons is the needs for, for example, a very long time planned data-to-rss-transformation system. This also means that we probably will deprecated the basic authentication system in a near future and start using JWT instead. For the DNS business, this may be a huge advantage in how data entries are handled in the editor.

To be continued…

Tornevall Maintenance and DNS updates

Posted on by

As our hosting conditions is about to radically change, the decision has been made to push away some of our DNS services. The services moved to Linode can not be used as recursive services. We’ve also completely removed the “microweb”-services, since they are practically empty and no longer necessary.

This is what’s happened during this weekend:

NS3.TORNEVALL.NET

  • Relocated to Linode DNS.
  • Removed service in JP

Removed

139.162.124.220
2400:8902::f03c:91ff:fe87:3989

Linode replacement

162.159.27.72
2400:cb00:2049:1::a29f:1a63

NS4.TORNEVALL.NET

  • Relocated to Linode DNS
  • Removed service in NL

Removed

141.138.204.6
2a02:348:83:cc06::1

Linode replacement

162.159.27.72
2400:cb00:2049:1::a29f:1a63