matcha_addict @ matcha_addict @lemy.lol

Posts

59

Comments

679

Joined

2 yr. ago

I know it's not the main point, but I wouldn't call Linux fractured. Linux has multiple choices, but they all work fine unless you're going into an experimental realm or uncommon distros that beginners shouldn't be getting near anyways.

NATO is an instrument of US hegemony. I can't imagine they'd stop committing to it. They know there are too many who think Russia is a threat to them and will just do whatever to keep NATO alive. I don't think US would want to let go of something so useful to them.

Well that's still good news that I didn't expect! I suppose I will look into that then. Thank you!

Do you know if it allows dependent tasks?

Not sure if it counts, but the terminal world being a place where many applications do so many different things but are interoperable, is amazing. I guess that would be the POSIX standard?

I wish there was a good open standard for task management or todo list.

I know there's todo.txt, but it lacks features like dependent tasks, and overall the plain text format limits features and implementations.

I don't think this is true. Turkey has been playing both sides for a long time, and this is just another step in that direction. But NATO is still resilient unfortunately.

I would even say XMPP would be a better underlying communication protocol under ActivityPub, as it specs many aspects that ActivityPub does not.

It may seem so due to its success, but I'd argue its success was more tied to luck and timing than technical superiority.

Mastodon was growing and "new" during the period of the decline of social media, and specifically during several moments of Twitter having issues with moderation, and later on acquisition by musk.

Similarly to lemmy, the Reddit third party API fiasco.

I don't think this means that it works better than anything else. It was just the most obvious choice to users at the time.

From my understanding developers often complain about activityPub. Can we really say that it "just works"? Federation and interop issues are common as well.

Hey nutomic! Thanks for adding the context. I hope my comments above didn't mis-represent what you said, and I'd like to add that I respect your position to not add a lot more work on the plate if it doesn't agree with your goals, especially when other platforms that do it exist (which is what I'm asking about in this post).

However I do respectfully disagree with the point on unix philosophy: unix philosophy also talks about interoperability, and you can see that with unix tools everywhere being very interoperable among each other. In my humble opinion, lemmy is not quite there yet with interop regarding other fediverse platforms, when that is a key benefit of the fediverse.

This isn't meant as an attack. This is surely easier said than done, and your work on lemmy has been amazing and I applaud it. But I also cannot confidently say lemmy is following unix philosophy in an exact sense here, not until interop is fully functional.

Cheers and thanks again for the great work!

But if the feature already exists in another platform, I'd gladly use that instead.

Plus, lemmy developers said this would be a very difficult change to make and requires a lot of rewriting. I presume it is because activityPub was only added to lemmy much later on.

AP doesn't really do this. A subscriber may be a dead account, or may be someone that hasn't checked your feed in months. Even a technical analysis would be difficult here.

I am responding to your point about RSS not having ability to discover new content whereas activityPub can. I summarized my point in the last paragraph. To reiterate, I agree that RSS doesn't have built in discoverability, but whatever ActivityPub has is not solving the discoverability problem. Let me know which part you don't understand please and I'd be glad to clarify.

I'd argue that discoverability on fediverse kinda sucks.

There's the network effect kind of discoverability, where someone you follow reposts something, and you discover this new something and possibly follow it. RSS has all the technology necessary to make this happen.

There's the discoversbility where you sort by "New" or "all" on your fediverse feed. I suppose that is discoverability that RSS doesn't have natively, but I'd argue this sucks pretty badly.

Last, there's the search engine type of discoverability, where you search through fediverse communities or users. This isn't native to ActivityPub, and a RSS search engine can be implemented pretty similarly.

In summary, So activityPub might have some discoverability paths, but the one that RSS doesn't have natively, I argue sucks and is not the right way to do it.

I fully agree with you, but I think this isn't because RSS clients can't do this from a technical perspective. I suppose most RSS clients come from people with anti algorithm sentiment, but realistically, a RSS client has all what it needs to implement basic or advanced sorting and filtering.

But I agree with you that most rss readers out there have that problem.

Thanks for confirming! However my question is if that's all, or if there's more. I assume you mean that's it.

I'd argue it's still a better representation than subscriber count. It is similar to the disparity between YouTube's subscriber count vs video view count.

From what I see, ActivityPub doesn't seem to solve the problem of sorting or prioritizing content. In fact, I believe RSS wins here, because it is easier to do this on the client side with RSS, as it is assumed the client has all the content from the RSS feed without any biased order, whereas with activity pub, it varies by provider and instance.

Sorting and filtering can be done well on the client side, and the plus side is the user can have a ton of choice here. It just so happens that our algorithms for that in the open source world are no match for the addiction-inducing ones of Twitter and others.

So activityPub uses push architecture to push to other servers / instances, but it doesn't push to users does it? I would imagine from instance to user, it is still pull based.

So effectively it's a load distributer thing, I suppose, right?