Tornevall Networks

Forum => Forum.

Forum => Socials (?).

Order on our Website below

URLS are removed due to spam.

/Admin

Order on our Website below

Order on our Website below

Innan du tycker det är roligt att en högerextremist bjuder in en vänstervriden till att följa deras sida bör du läsa igenom detta. Du är nämligen varken speciellt utvald eller särskilt unik i urvalet.

Många på sociala medier (Facebook) finner det fortfarande än idag ganska komiskt att just dom blivit inbjudna till en sida som de själva inte sympatiserar med? I mina kretsar rör det sig framför allt om “bloggare” som Joakim Lamotte och andra som är aktiva i högern. Men det är egentligen inte särskilt konstigt att det sker. Om sanningen ska fram så lär dom inte ens känna till att det är dig dom bjuder in.

Varför? För att det sker automatiskt!

I Facebooks business-del har det under aviseringslistan en knapp för att automatiskt bjuda in 20-25 personer. Automatiskt till den grad att du måste välja att klicka på den för att det ska gå iväg så många samtidigt. Det finns också andra sätt att bjuda in folk på genom manuell hantering på respektive inlägg, genom att gå igenom alla reaktioner och klicka på “Bjud in”.

Varje gång du klickar på “bjud in” så måste man ladda om sidan för att man ska få lov att skicka ytterligare inbjudningar – fram tills de börjar ta slut. Vad Facebook gör här är att hantera inbjudningar snabbare än om man skulle gå igenom en och en ute i de inlägg man skriver. Det kan se ut så här:

När jag går in i mitt verktyg och ska försöka göra ovanstående skärmdump, möts jag även av detta:

Inom kort verkar det alltså komma ytterligare nya funktioner som kanske gör att du slipper göra det här helt och som gör att du som inbjuden kommer kunna skratta ännu mindre åt det.

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​

​

BBCode seems to work in regular forum posts, but not in some user profile fields. The issue is most likely related to how vBulletin handles profilefields, where some fields appear to be treated as plain text and therefore do not render BBCode or automatically convert URLs into clickable links.

This also affects the "Web" field, where links are not made clickable.

Signatures seem to work better, but some older signatures may have been affected by a previous database conversion. That conversion also caused character encoding issues earlier, including å, ä and ö being removed from parts of the forum content.

A possible fallback could be to detect plain-text URLs with a regex, for example:

Code:

https?://[^\s

Vi har justerat teckenstorleken i forumet baserat på önskemål från våra användare. Vi förstår att den nya storleken kanske inte passar alla, så vi arbetar på att möjliggöra anpassning på profilnivå. I profilerna finns en inställning för fontstorlek, som ännu inte fungerar helt, men vi förbereder den så att varje användare kan justera sin egen storlek.

We've had questions about both Mastodon and Bluesky integrations, especially around how they could connect to the forum.

The main reason this forum exists is that we want to avoid becoming dependent on third-party platforms (which we in vBulletin already are). Because of that, it would be counterproductive to move our core activity to a service where we rely on someone else's software, hosting, infrastructure and legal environment.

Mastodon is currently rooted in Germany, although the project has been working on a broader European non-profit structure. BlueSky is based in the United States. Both platforms support decentralization in different ways, but we still prefer to keep our own stable base in Europe, and preferably in Sweden when possible. But that does not mean integrations are off the table. It may still make sense to connect the forum to other services when they solve a specific problem, as long as the forum itself does not become dependent on them.

For example, we could eventually look at optional connections to Google Drive or Microsoft OneDrive if we need extra file storage that we cannot provide here. That is a separate topic, and something we can come back to later.

Bara å köra

image.png