I dont want any parts of Threads. But if they’re gonna federate, at least do it 100%. This half-ass, piecemeal approach where they release an itty bitty teeny weeny change every month is weird.

Not many things require a polyfill these days. My guess is a lot of older sites are affected.

The clients are called “RSS readers”. Most blog sites have RSS feeds you can add to it. And there are services that can easily generate RSS feeds for websites that don’t already have them.

I never really understood how cross posting works here. You mind telling us the benefits? Does it consolidate all of the discussions in each cross post into one big long thread? 🤔

A website can access another site’s cookies if the first party domain explicitly allows them, which would need to happen in this case. Sure, admins would have to allow which sites can access the cookie. But at least that burden is placed on admins vs the users.

Browser extensions arent secure and many mobile browsers dont support them, so that wouldnt be a proper solution. A lot of users use Lemmy on their mobile phones.

Sites can still have third-party cookies. The first party domain just needs to explicitly allow them.

Was about to ask if there was a way to do this automatically. Does anyone know why this isn’t baked into the Lemmy codebase? I’m thinking this would be pretty easy with browser cookies. 🤔

If you use RSS feeds, there is. There are services that provide RSS feeds for Lemmy posts. You can subscribe to those and get an update whenever any comment is made on the post.

As an engineer who’s worked on very large codebases over two decades, I’ve realized that this is so much easier said then done.

If people want to fork Mastodon, great. But they’ll quickly realize that what they may think are straight-forward “improvements” will lead to them having to address bigger architectural issues.

Many design decisions that were made when building Mastodon may not be perfect, but they address a lot of very complex decentralization and federation issues.

There’s no such thing as perfect software. What some may think is an improvement, others will think is a terrible choice. Each decision is a trade-off and will have downsides. We just have to decide which of them we’re comfortable with living with.

These were great in their day, but it’s time to move on to something better and safer.

How is it “safer” when contributing to the codebase or filing and discussing issues will now require creating an account and giving up personal information to one of the most privacy-invasive tech companies in the world? 😳

Oh neat! I didn’t know this existed. By any chance, do you know of any RSS readers that have implemented it?

Yeah, depending on the branch I’ve found that method not to be too reliable. openrss offers branches for RSS feeds for commits on every branch though: e.g. https://openrss.org/github.com/octokit/octokit.rb/commits/main

Maybe Vimeo?

I often wonder if FAANG’s determination to find who can write the best algorithms backfires, and may be the reason a lot of the work they produce seems so over-engineered.