Yeah I’m not disappointed to see this instance close up.

Theirs is a “Loli/Shota/Cub Friendly” instance according to their sidebar. That’s why they aren’t federated with many instances.

The default UI is how most new users will experience interacting with lemmy instances at first. So it’s helpful to create a better first impression. To the extent that this is built into the project itself makes it easier for other UIs to be created and maintained too.

I believe that the Lemmy devs are working on a better url scheme for posts and comments as well. This will also make it less annoying without any browser extension, script, or other third part service.

I generally agree with you.

However, I want to encourge you to consider softening up your replies to people who you don’t have a strong prior social connection with. I’ve started making an effort to do that and I’ve found that I’m having more rewarding conversations now.

That’s very different from what I think people generally want by default, which is that when you’re on lemmy.world, it’s because that’s your home instance and any links to other instances would be automatically converted to the lenmy.world version of the post or comment by default (as long as the two instances are federated).

Anyone that wants more could find a browser plugin or script, but every new user with an account of any instance would have an initial experience that’s much less confusing and more consistent and pleasant.

It’s not implimented because the developers of lemmy have been prioritizing other issues and features. They say they’re open to code contributions, so someone would have to volunteer to do it.

Why would you need another site’s browser cookies?

With BlueSky, it pretends to be similar, but the reality is that everything needs to go through their central server in order to be displayed on a timeline.

They have been saying that this is an implementation detail that will change when they open up that part of their implementation. Which is nice, but until that happens I’m only lukewarm in my optimism for Bluesky and the AT protocol.

On the other hand, every federated network has converged on a central host for the vast majority of accounts and data. That host has outsized influence over the standard used on the network and unencrypted acess to the majority of data. So I’m not sure what really matters to what extent.

Isn’t that the same issue with ActivityPub and the instances that host accounts and messages?

Mastodon’s moderation model is very different than BlueSky. BlueSky’s seems to be much better for targeted individuals and groups. But things aren’t entirely hashed out on either protocol or their implementations. We’ll see how it goes.

My first exposure to that interchangable use in the Lemmy lexicon. Now I Know!

That was exactly my thought when asking. But it seems it’s the former.

Thanks for clearing that up!

What’s a Lemmy group?

Since storage costs money, does it allow the admin to offer tiered access to higher quality storage?

They all seem reasonable suggestions:

• Consent matters, even for public posts
• Get broad feedback before launching – and listen to it
• Honor existing opt-in and opt-out mechanisms
• Include an additional opt-in mechanism for your service if it’s not just a search engine or profile discovery (or something very close to them)
• Make sure to communicate that you’re taking an opt-in approach and honoring existing mechanisms
• DON’T say the things that developers who ignore consent typically say
• Be extra careful if you’re a cis guy
• Look at opt-in as an opportunity for a potential competitive advantage

I’m conflicted over the fact that using ActivitiyPub necessarily implies consent for other people to collect the data you send through it. It seems that many people using ActivitiyPub connected services want something different than ActivitiyPub or different default settings on many ActivityPub services.

I’d like to see this experiment carried out at a sufficient scale. I feel like there would be a benefit to a gravity like component that takes density and distance into account so that people in sparsely “populated” regions aren’t just effectively seeing an unprioritized feed of the entire network.

If you don’t post one, all copyrights are reserved by the author and is automatically granted upon publication in most jurisdictions around the world. So every federated instance is violating every copyright.

That is unless it’s seen as fair use, in which case it doesn’t matter what licensing the author wants to provide because the use is protected.

I wonder if the legacy webhooks implementation in Lemmy has left some artifacts that show up when the services that comprise Lemmy are split up as they are for larger instances.

This is pure speculation.

This is probably the most reasonable take. But I remember getting tipped and not ever bothering to follow the link to try to collect until a few months later when the service hosting the crypto thing went permanently offline and couldn’t be collected.