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.

Yeah open rss has Lemmy feeds that always link to your instance.

What do you mean by multi communities?

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? 😳

We’re talking about instances having feed content for other instances (on totally different domains), so anything helping with this case would be a “third party service”.

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

You can use openrss.org RSS feeds. They are there for this exact purpose. For example, you can get an RSS feed of /c/retrogaming@lemmy.ml by going to https://openrss.org/programming.dev/c/retrogaming@lemmy.ml. Then all links in the feed will always go to the post on programming.dev instance.

Is there one for the other sites like bbc.com?

I love a friendly debate 😀:

The statement says How can you steal something that the customer cannot own?. You can definitely steal it if “you” aren’t the customer. And you can steal it from a “customer” even if the customer doesn’t own it and someone else does. And you can steal if even if you are the customer, because you aren’t the owner. The only time you can’t steal it is if you are the owner, because you own it.

The definition of “steal” you mention seems to be proving the point I’m making. Something can be stolen if the person stealing it isn’t the owner, which is the case in the first three examples I mentioned above.

The statement is an odd play on words and loaded with assumptions that are left up to the reader, which is why it’s super weird to use it to try to prove the point the author was trying to make.

if buying isn’t owning, then piracy isn’t stealing. How can you steal something that the customer cannot own?

By stealing it? You dont have to own something to steal it. Or maybe I’m reading that wrong. Lol it’s a very interesting take but I like the spirit of it… And it made me laugh. Cool 😎

WOM has and will always be the best form of marketing and you dont need big marketing teams to do it.

The problem is that a company doesnt need that many people to push a product. They can just pay the few they need, well. But instead, they’d just rather hire a shit ton of people and under pay all of them.

This reply reads like we should have to pay for these big unnecessary marketing teams these companies hire, which shouldn’t be the case.

Just depends on what works best for each of us. But personally, I agree with you. It’s not that I think one company owning a ton of the services is a bad thing in itself. But history has shown us that, when a company starts to dominate a certain market, they tend to start becoming tone-deaf to our interests, because they know we can’t (easily) switch and go somewhere else.

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

Sure but new versions are released pretty often, which essentially means they can change their license whenever they want.

Interesting idea. A couple questions:

How would it work if the open source maintainer is a commercial company?

AFAIK there are no restrictions on when an Open source maintainer can change their license. They can do it even after their work has already been used.

So couldn’t a company like, Facebook (since they own open source React) just change their React license to this one and all of sudden start charging everyone for it? 🤔