https://forum.tornevall.net/ Special category. en Mon, 08 Jun 2026 04:55:14 GMT vBulletin 60 https://forum.tornevall.net/images/misc/rss.png https://forum.tornevall.net/ https://forum.tornevall.net/forum/tools-api-dnsbl/1063455-vbulletin-vs-openai-and-security-measures Sat, 06 Jun 2026 15:43:28 GMT Den här texten återges på Svenska i nästa kommentar. There is a generally understandable skepticism around the use of AI - not only from me, but from others as well. A discussion in the vBulletin forum raised some important concerns about security, data protection and how forum content is handled when AI tools are involved. In our case, the current OpenAI integration is still an early prototype. We have not yet built the full privacy and consent layer around forum content, and that is exactly why this feedback is important. The intention is not to silently send full forum discussions to an external AI provider, especially not when the forum are hidden, closed or private. AI usage should be explicit, configurable and limited by clear privacy rules. Since data may eventually move between the forum, Tornevall Tools and/or an external AI provider, we need to treat that data flow as... Den här texten återges på Svenska i nästa kommentar.

There is a generally understandable skepticism around the use of AI - not only from me, but from others as well.

A discussion in the vBulletin forum raised some important concerns about security, data protection and how forum content is handled when AI tools are involved. In our case, the current OpenAI integration is still an early prototype. We have not yet built the full privacy and consent layer around forum content, and that is exactly why this feedback is important.

The intention is not to silently send full forum discussions to an external AI provider, especially not when the forum are hidden, closed or private. AI usage should be explicit, configurable and limited by clear privacy rules. Since data may eventually move between the forum, Tornevall Tools and/or an external AI provider, we need to treat that data flow as something that requires careful handling.

We are therefore planning to keep building the AI integration with extra privacy and consent in mind.

The goal is to make AI assistance optional, visible and controllable. Administrators should be able to decide how much context is allowed, which provider is used, and whether AI features should be available at all in sensitive or private areas. But in the end, users should have the full right to control their data.

To address this, we are planning support for several privacy options (since this is a product for vBulletin, the plan is to make it generically controllable for anybody):

- Request only - only the user's own AI request is sent.
- Thread context - surrounding thread content may be included, if allowed.
- Consent required - content is only included from users who have explicitly allowed it.
- Opt-out mode - content may be included unless a user has opted out.
- Disabled - AI context handling can be turned off completely (on user level).
- Private node protection - private or restricted areas can force request-only mode.

We also want this to be configurable both globally in AdminCP and, where relevant, at profile level. A user's profile setting should be able to override the global setting when deciding whether their content may be included in AI context. It should also be possible for a user to disable AI context usage for their own content.

Another important point is provider visibility. Users and administrators should be able to see whether the configured AI route is:

- Tornevall Tools
- Direct OpenAI
- Another internal or custom provider in the future

This matters because consent to one provider does not automatically mean consent to another. Also, since we have funding issues, we should not handle ALL traffic from all forums in the entire world - that is a very stupid way to build this solution.

For closed, private or sensitive groups, the safest behavior should be the default: if the system cannot determine whether content may be used, it should not include that content. Quotes, signatures, attachments, embedded media, deleted posts, hidden posts and moderated content should not be sent as AI context by default.

The basic principle is simple:

A closed and safe group must remain closed and safe even when AI tools are enabled. External AI use must be explicit, explainable and easy to decline.

This feedback is useful and will be taken into account as the integration develops. The current implementation should be seen as an early prototype and proof of concept, not as a final architecture that every vBulletin installation is expected to use. The long-term direction is a more flexible setup where each forum administrator can choose the provider, data flow, consent model and security level that fits their community.

Follow the project at github, where you can also raise tickets for the product:
https://github.com/Tornevall/tools-vbulletin-ai​
​]]> Tornevall https://forum.tornevall.net/forum/tools-api-dnsbl/1063455-vbulletin-vs-openai-and-security-measures https://forum.tornevall.net/forum/tools-api-dnsbl/1063419-toolsapi-fix-now-you-can-request-full-access-to-openai-as-a-developer Sat, 30 May 2026 06:07:57 GMT
We have just fixed the "OpenAI Access Request" section in Tools, which could previously cause 500 errors when submitting requests to get full access to the OpenAI-API.

This part is not related to "Tornevall Networks Social Media Tools". It is a separate part of Tools intended for developers who want direct access to the API.

Additionally, we want to keep you informed about our budget considerations. As we work to enhance our services, costs may increase significantly. However, we are actively developing a donation solution that will allow users to contribute and help set a sustainable budget based on community support and membership options.

Thank you for your continued support and understanding.
]]> Tornevall https://forum.tornevall.net/forum/tools-api-dnsbl/1063419-toolsapi-fix-now-you-can-request-full-access-to-openai-as-a-developer https://forum.tornevall.net/forum/tools-api-dnsbl/1063390-trustpilot-but-for-social-media Tue, 12 May 2026 19:39:39 GMT "We have started laying the foundation for Trustpilot for Social Media.

The idea is simple: people should get better help understanding whether a website, link, post, or source seems trustworthy, questionable, or worth checking more carefully.

Today, we often meet information without any useful context. A link appears in a feed. A post gets shared. A website looks serious enough. A claim is repeated often enough. And suddenly, people are expected to decide for themselves whether it deserves trust.

That is not always easy."

Full article can be read below:

https://www.tornevall.net/2026/05/12...would-it-mean/]]> Tornevall https://forum.tornevall.net/forum/tools-api-dnsbl/1063390-trustpilot-but-for-social-media