valuesubtracted@startrek.website CTV SciFi is still an add-on channel, which is unfortunate for freeloaders like me (I use an antenna which probably makes me a crusty old fart.)
In the ideal case every connected server should host a full and complete copy of the data from the originating server (as xkdrxodrixkr@feddit.org says, that's B)
Reality is a bit different, but not enough to warrant always picking B. Just share whichever you'd like, but B is the most right.
NodeBB also does this, and currently still does. A category (group actor) can follow another category (also a group actor).
It essentially is synchronization of categories using 1b12.
Proof of concept does work but it needs reworking in some ways. The largest issue is that Lemmy itself doesn't understand when a group actor tries to follow a community.
Tell me about it! There are some very cool people (i.e. thisismissem@hachyderm.io) working on content classification and tagging so that the burden of filtering out this kind of content isn't borne by server admins directly.
snoopy@jlai.lu personally, since I create AP enabled software I am on the side of votes being public data. We already have enough issues with votes being out of sync with each other. Mixing in private voting is just asking for trouble.
Emoji reactions are neat, although niche to those softwares that utilise it. They allow for greater expression which is nice. They're useless for deriving value (for ranking purposes) unless you assign value to them.
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.)
Very interesting article! I have immense respect for jerry@infosec.exchange, 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.)
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.
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?
m_f@discuss.online 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 evan@cosocial.ca and j12t@j12t.social finally have write access to the repo and control of the domain.
occultist8128@infosec.pub "followers only" is a concept that is Mastodon specific, and Pixelfed supports it.
There's nothing to change at the protocol level itself.
Sending the reply to OP in your example would be a betrayal of the visibility of followers only... which is kind of silly but technically correct.
Better would be followers + participants, but that's up to the individual implementors to adopt.