Topics tagged with threadiverse

Fedilab has opened a nodebb forum

Invalid Date

Julian Lam - Forums over Feeds: End the doomscroll

kentnavalesi@mstdn.social — Invalid Date

@julian@fediverse People always of think of the algorithm as something that delivers content -they don't think about the things it filters out.

Mbin v1.9.1 release (stable)

die4ever@retrolemmy.com — Invalid Date

Each magazine has a Tags page in which moderators of the magazine can set the hashtags by which microblogs are put in this magazine. Previously we used the name as a tag as well, without telling the user and without a way to disable it. We now add the name of each magazine to its tags page to make this behavior clear and to provide a way to disable it. When creating a magazine, we added a checkbox to add the name as a hashtag sounds good

Coming soon, a new /world experience

Invalid Date

Cursed hack to fix Mastodon-Threadiverse communication

julian@activitypub.space — Invalid Date

NodeBB now sneaks in a mention to the category/community, and this gets pre-filled in the Mastodon composer. I tested it against piefed’s crust instance, and the response from Mastodon to my post on NodeBB successfully made its way to crust for distribution @rimu@piefed.social [image: 1772652313700-020a80cf-d0b0-4fbf-aa5a-20b951a109ef-image.jpeg]

Cross-posting is coming to NodeBB!

julian@community.nodebb.org — Invalid Date

> Just from a cultural homogenization point of view, it’s been a negative. You’re not wrong, and so I think the future of this is meant to be opt-in rather than opt-out. Realistically what a two-way opt-in looks like would be: A topic is created A cross-post request comes in OP (or mod) approves or rejects Topic is cross-posted. However that in general introduces a significant amount of overhead and mental burden that would disincentivise usage of cross-posting. I’m not sure what the answer is. I used to be very bullish on the idea that cross-posting would solve so many problems via inteconnection, but there are some very significant social concerns that would absolutely taint the very idea. So, we tread carefully.

Context removal from an audience

Invalid Date

Threadiverse... on ATProto?!

flamingos@feddit.uk — Invalid Date

All the data is stored in the nooki PDS. And there is one nooki PDS and can only be one PDS? Or can anyone make one? Users have PDSes (Personal Data Server). Nookie wouldn’t have a PDS, it could have its own database but that’s not anything to do with the protocol. The theory with ATProto is that user facing interfaces (App Views) write data directly to PDSes and then this data is aggregated by a giant index (Relays). This relay data is then consumed by those App Views that sort them into posts, replies, likes etc. and presents it to the user as a usable interface to interact with. That’s the high level gist, Bluesky is ridiculously over-engineered as it’s made by a bunch of cryptobros who wanted ‘social media but on the blockchain’ originally and this bleeds into the wider ATProto ecosystem. I can’t speak for nookie, it could just be a basic centralised site that uses Bluesky as a sign-in mechanism. (That’d make sense given the apparent author prompted it here before and didn’t say it had any ATProto integration and it used to have the ability to create accounts).

ForumWG canceled this month (June)

Invalid Date

Automatic category/community assignment on received object

julian@community.nodebb.org — Invalid Date

I suppose you’re right in a way. The context owner is not supposed to be set by someone other than the context owner. It’s a fallback mechanism intended for better compatibility with Mastodon. When a group is addressed and it is one of the local NodeBB categories, it will assume control If it is another group that it knows about but isn’t same origin to the author, then no category is assumed.

What would cross-posting between instances look like in ActivityPub?

julian@activitypub.space — Invalid Date

It was noted that there were some social barriers that would be crossed if federated cross-posting were implemented. Namely, tribalism exists in all corners of the fediverse (related; see Jaz’ “million fediverses” blog post). It is more pronounced in the threadiverse because there are explicit fences around communities, e.g. sports team, political leanings, etc. There is the potential for abuse to occur if cross-posting were made available to users. e.g. enabling dogpiling by cross-posting to a community who does not share the values of the original post. In and of itself that’s not a reason to not move forward with this. I went ahead and implemented cross-posting in NodeBB itself, but only locally. That is, remote posts can be cross-posted to local categories, but not the other way around. It’s worth noting that me doing this already enables the dogpiling behaviour, though NodeBB forums in general aren’t really all that tribalistic so in practice there have been no issues. As far as I know, Piefed and Lemmy still treat cross-posts as separate entities. However, they both have independent implementations where similar posts (those that have the same Link, I think) are “linked” in a manner of sorts. Browsing the comments of one post would show comments from similar posts across different communities. NodeBB does not do this because we do not group content together by Link.