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.
Press any key to continue… No, not that one!
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.
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 .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.
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.
I hope you’re right!
Maybe Vimeo?
sigh So Threads can throw their posts out into the fediverse, but no one from fediverse is allowed to post comments back? Why am I not surprised? 🙄
Signal app is great. Would that be a better alternative? Or is that too niche for Discord users?
Have you tried the Signal app? Has all that and works pretty well!
Exactly what I was wondering the entire time I was listening. None of these questions were asked during the episode. A lot of handwaving and buzzword double-speak. She didn’t go into any real technical detail.
Sorry, that’s not what I meant. The AT protocol has been available since they began. So anyone could have built apps on it all this time. Federation isnt required for their protocol to be used.
I just haven’t seen any entirely working apps (made by non-Bluesky devs) using their protocol yet. And they totally ignored using or improving ActivityPub. So it comes off as their just kind of building their own thing, which is a centralized way of thinking.
They would’ve been better off building Blusesky on ActivityPub, an open protocol that’s already battle-tested and in use by a number of different apps and made my different developers. But building a whole new protocol that no apps are using has the same net effect as if a centralized company like Instagram Threads were to do it.
If you’re saying there are non-Bluesky apps using their protocol, can you link to these apps here in a reply? Totally open to being corrected.
Not the person you replied to. But I think they meant that Bluesky is using a protocol that only the company uses.
Sure its a federated and decentralized protocol, I guess. But if they’re the only platform using it, it’s still rather centralized in that regard.
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.