Does anyone remember way before Google had image recognition technology, the time they built a game that paired up random people on the internet, showed them each an image, and waited for them to both guess the same keyword?

It was gamified human powered taxonomy for meaningless internet points and it was hilarious (at the time.)

[email protected] A little bit, yes! There was a recent thread in the community I posted to where a discussion about the rather lacklustre search of various software took place.

Very interesting article! I have immense respect for [email protected], he was one of the first people I found on the fediverse, and it’s no wonder why, he’s revered quite highly by others as being a generous and kind admin.

I do want to point out one thing, and that is that Mastodon has some design decisions that make it rather resource and storage intensive.

There are oodles of lighter software out there, some with even more features than Mastodon, and some with less. For example, snac.bsd.cafe (https://snac.bsd.cafe/) runs on Snac, which is fast as hell.

I am going to guess that a not insignificant portion of Jerry’s bill is caching assets. Mastodon likes to save everything it encounters, videos, images, avatars, everything… forever (though I imagine this is customisable). Most likely the assets are viewed a handful of times in one day and never seen again… but you’ll pay to store it forever!

Thanks! It’s something that I personally feel is more performant and future proof for other important things like private discussions (which Mastodon also doesn’t support natively yet — mention spamming doesn’t count.)

Sure, check out my post about it here:

https://community.nodebb.org/topic/18844/backfilling-conversations-two-major-approaches

There are steps being taken in the right direction.

Lemmy and lots of other software use a fediverse extension called 1b12 to keep everything in sync.

In a nutshell it means Lemmy communities can follow other communities, and they keep each other in sync. The same applies for other types of communities, like PieFed communities, Mbin magazines, NodeBB categories, etc.

Mastodon doesn’t have a concept of community or categories, so they don’t support this kind of synchronization.

There’s NodeBB if you want a forum/BBS style UX for the threadiverse!

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.

[email protected] yes, it should. Mentioning the category means it will be addressed and NodeBB will slot the received content in the first group object it finds.

Yes, NodeBB does travel up inReplyTo. I’m not sure why it isn’t working for some Lemmy topics currently.

[email protected] it’ll work better once cross-posting is built into NodeBB I think :smile:

> One weakness I have noticed in NodeBB’s current federation is that posts which are in reply to a topic (e.g. a Lemmy comment) show up as individual threads until (or if) the root post of that topic shows up in the local NodeBB.

No, Lemmy does not implement either strategy, they rely on 1b12 only.

If NodeBB is receiving parts of a topic that don’t resolve up to the root-level post that might be something we can fix. I’ll try to take a look at it.

[email protected] said: > If the OP is the single source of truth, they can moderate the entire conversation (represented by context collection: Streams). If not, then each reply is independent and authors moderate only the direct replies (represented by replies collections: GoToSocial).

That is a good point. The approaches are broadly compatible when top-down moderation by the context owner is not assumed.

In a moderated scenario, crawling the reply tree would not be useful unless paired with some sort of “is member of” validation with the context owner… at which point the served collection would be more performant.

It could be useful for discovery by the context owner itself though.

For what it’s worth your blog does show up fine in NodeBB as well. Perhaps you are missing the @context property and so Mastodon is refusing to parse it?

Hi [email protected]! This could be related to some better support for non-Note types introduced by Mastodon in later versions. Your instance is running v4.1.18 which is 11 months behind the latest version.

That isn’t necessarily cause for concern, but I think that might be why you’re seeing the HTML tags?

[email protected] not directly, but there was a session at FediForum on Thursday that discussed the website and next steps for updating it. It’s been stagnant for quite awhile but [email protected] and [email protected] finally have write access to the repo and control of the domain.

[email protected]

beep beep boop boop boop boop beep… EEEEEEEEEEeeeeeeee awwwwwww ka-dong ka-dong da kshhhhhhhhhhhhhhHHHHHHHHHHHHHHHHHHHHHHHHHH

eerie silence

you can still have it with NodeBB!

Hey [email protected] have you tried updating to the latest NodeBB? You can post to Lemmy communities from there too!

[email protected] ActivityPub.rocks I bet?

There’s exciting work planned for updating this site!