TheOneCurly

I don’t believe it’s possible for a CA to decrypt TLS traffic with their private keys. They sign a site’s public key with their own private key after verification but are never given the private key itself. Public CAs only provide identity verification, they do not take part in the encryption process itself. Let’s Encrypt is perfectly safe in that regard.

I see season 1-9 packs on both IPT and TL.

To be fair that’s a pretty recent development. Jellyfin apps for smart tvs are only just becoming stable enough for real use. Plex was the only option for a long time.

I run Lemmy, Plex, and a bunch of other services from a desktop in my basement. It works great. The Lemmy docker setup is a little finicky but works well once you get it.

There are quite a few creators who are primarily funded off patreon and release content to YouTube. I imagine a group like MCDM (Matt Colville) who has patreon, merch, crowdfunding, and products doesn’t really care about ad revenue.

I don’t believe so. I’m not sure what their long term goals look like.

There’s no need to run an LLM on the same system it was trained on. Once the model is built it contains all the information already. If you want a model to live on long term you would just release the file(s) publicly, like hugging face does with theirs, then anyone could use it or host an interface for it.

Your instance would have connection logs for whatever browsers or mobile apps you used, but other instances talk directly to yours and know nothing about you. So use an instance hosted in a jurisdiction you’re comfortable with or like you said tor or another basic vpn is plenty to anonymize you.

Lemmy federation only starts when a user on your instance searches for and subscribes to a community on another one. So unless a user on your instance goes searching for cp it’s not really an issue.

They also host their own f-droid repo if you want one built by the developers and not f-droid. https://fdroid.fedilab.app/repo/

Nope, I’ve seen nothing firm about them doing or not doing it, but OP asked about current information and at the moment they are open source and do not have a standards document.

As it stands I wouldn’t jump on AT for a project of mine and wouldn’t recommend it as a superior protocol on those grounds.

So when Bluesky introduces a new feature or a breaking change in the protocol anyone downstream will find out when it gets pushed, maybe a little ahead of time when it comes in as a pull request. Bluesky goes live with the change immediately, maybe in a public beta channel, maybe straight to prod, depending on their testing setup. Anyone running a bluesky compatible server becomes immediately incompatible until they rush to implement the new changes. The best user experience will be had on first party servers, driving the vast majority of users there.

For a standard defined protocol, like ActivityPub for example, to introduce a change like that it would first go to the standards comittee where it would be discussed publically with stakeholders. The changes would be published and then all parties would begin implementations at a pace that makes sense to them. It’s like when you hear about new Wi-Fi versions several years before any devices actually support them. One group doesn’t just get to come out with some crazy new change that everyone else has to reverse engineer and then race to keep up.

What Bluesky is doing might be fine and make sense for their model, whatever that may be. I just want to point out that there is a difference and it drastically changes what the future of the service will look like.

Bluesky’s protocol implementation is open source but the protocol isn’t defined by any standard. Once its open and federating, if that ever happens, anyone who wants to connect will be entirely beholden to the latest published version from bluesky and whatever protocol documentation they provide. They’re starting in the middle of the EEE playbook, anyone who wants to join in has to chase them.

As far as I know AT isn’t actually being used anywhere at the moment. Bluesky has a single server with closed registration and no federation partners. Despite being open source, AT isn’t really intended to be an open protocol.

ActivityPub, on the other hand, has a few hundred servers including several dozen large ones all federating nicely together.

Kbin calls them magazines. Same thing.

I know following users was a pretty big sticking point on reddit, it was certainly a feature I had no interest in using, but it’s a lot more interesting here with federated interoperability. Regardless, I think it’ll be a while before the lemmy devs even have time to think about features like that.

At the moment Lemmy and Kbin federate exactly, Lemmy communities and Kbin magazines federate 1:1 with upvotes, downvotes, comments, all working as expected.

Mastodon users can follow communities and magazines as though they were users, post to them, and see replies. Although they see everything linearly. If you ever see a community post that starts by tagging the community that likely came from mastodon.

Lemmy does not currently, and may never, allow you to follow mastodon users or tags. Kbin offers a microblog view that does display mastodon content in its intended form.

Bluesky has their own proprietary “federation” tech they’ll be using, probably just with select partners. There’s no news right now that they have any plans to implement ActivityPub, which is the backbone of the Fediverse.

Threads, on the other hand, does seem like it will implement ActivityPub soon™. At the moment twitter-like and reddit-like sites don’t federate super well, but I imagine that will change at some point, especially when kbin gets a little more stable. So the most immediate impact will be between Mastodon and Threads but we’re not far behind.

Says they don’t want to do it

Does it anyway, as soon as its released.

It’s ok to just say you want something.

“Your instance”