Thanks j12t@j12t.social! Still tweaking things a bit but planning to do an announcement in short order. Excited to see topical carve-outs of the fediverse... I think it has legs, let's see if my bet pans out.

bentigorlich@gehirneimer.de melroy@mastodon.melroy.org see that's the thing... You guys are active, and on the fediverse, but not on the subset of the fediverse that smallcircles@social.coop sees... the Threadiverse! ... and why wouldn't you be on the threadiverse, it's more relevant to mbin than the microblogiverse. That disconnect is something I'm hoping to better address very soon. julian@activitypub.space

lepertti@mastodon.gamedev.place yes! That's what I did with NodeBB. The main things you need for that are the content discovery pieces, otherwise you're broadcasting only.

tom@tomkahe.com That's a fun idea... I'm doing it (using FetchRSS, though) in NodeBB. community.openbeta.io pulls in a bunch of climbing news websites via their RSS feeds and re-publishes it onto fedi

silverpill@mitra.social I wasn't aware that there were sections pertaining to context. I'll have to review more closely.

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.

@miaq@flipboard.social @jerry@infosec.exchange for sure, just look at the number of instances spanning multiple software!

Good lord @liaizon@social.wake.st did you just necro a 3 year old topic