Fediverse

No, Firefish died off some time after it was rebranded from Calckey. (that’s the short explanation)

I dunno, I like pie. I like piefed.

Thanks for posting about this thenexusofprivacy@infosec.exchange I’m interested (in a tired defeatist way) in what I need to do to stay on the right side. It sounds like geoblocking is probably the quickest legally safe course of action, so perhaps it’s bye Mississippi too…

Well, the good news is at least with conversational backfill, you’ll be able to pull the entire reply tree

jgrim@discuss.online Pixelfed has no versioning? That’s concerning that you have to live on the bleeding edge if you don’t want to be outdated. I do see there are tags, which at least shows some versioning?

troyunrau@lemmy.ca fwiw the organizers are quite transparent with how the tickets are priced and where the money goes. Hosting a conference, even one that’s online, does take money.

I think maybe posting each individual video to this community might be helpful so individualized discussions could take place.

That is completely on brand with how the Ghost team operates. It’s wonderful to see.

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.

pumpkindrama@reddthat.com NodeBB supports topic based following, because it’s a forum and that’s literally how it was done way back then. You can follow tags as well.

Loops is newly funded, so that round is still active. I still wouldn’t get hype about it until it happens though!

Theoretically, it shouldn’t matter. 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.

Yes. When the reply is posted to C, it is sent to A. A then sends as:Announce to C, as well as any other communities that follow it. B seems to be irrelevant here.

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.)

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