[-] [email protected] 8 points 2 years ago

Not only that, but Meta is even claiming that they don't have any former Twitter employees. Sounds like Musk is projecting. Either that, or he's grasping at straws.

[-] [email protected] 9 points 2 years ago

As long as that's optional. I'd much rather know exactly which community I'm looking at.

[-] [email protected] 20 points 2 years ago

That's cool, but OP is specifically asking about finding things on Google.

[-] [email protected] 11 points 2 years ago

Asymmetry can be hot. Observe:

74
Rule (lemmy.world)
submitted 2 years ago by [email protected] to c/[email protected]
[-] [email protected] 3 points 2 years ago

I am super duper excited!

[-] [email protected] 21 points 2 years ago

From a developer role, Lemmy is going to need to figure out a way to scale up development.

No they don't. The platform is open source, so the more users they have, the more of those users will become contributors.

[-] [email protected] 4 points 2 years ago

That would just make them go downhill further.

[-] [email protected] 5 points 2 years ago* (last edited 2 years ago)

I was thinking about the multiple accounts thing. Maybe the concept of an "instance" needs to be separate from the concept of an account? Like, it doesn't matter what service you choose for your email account; you can email anyone from Gmail, and anyone can send email to you. The only real difference is that your email address end in "@gmail.com" instead of "@comcast.net".

On Lemmy, though, the place you make your account matters a whole lot. It determines what content you're allowed to see, and who you're allowed to interact with. If the instance you're on gets federated, you need to migrate to a different account on a different instance. That never happens with email!

A lot of users have been managing this by creating their own instance, with the sole purpose of hosting their account and nothing else. Maybe that's what we need: a set of "instances" that only host accounts, and a set of "instances" that only host communities. You could then use that account to subscribe to communities from any instance. That way, Beehaw could block content from instances they don't like, without cutting off all of the users who happened to choose the wrong place to sign up.

Actually, under that system, there wouldn't be a need for instances to federate content with each other at all. Users could just subscribe to communities with their account, and then the users would be the ones in charge of what they see, instead of their instance choosing for them.

[-] [email protected] 4 points 2 years ago

I got that vibe when I saw that they intentionally keep their rules vague, to make them harder to evade. That just sounded to me like a recipe for power tripping.

[-] [email protected] 5 points 2 years ago

He already publicly admitted that Reddit isn't profitable. I'm sure that inspired tons of confidence in investors.

[-] [email protected] 15 points 2 years ago

I'd rather people not delete their content at all, tbh. Imagine all of the Google searches that would be borked by it.

[-] [email protected] 3 points 2 years ago

I tried kbin, but I left it behind when I realized I couldn't tell the difference between federated and non federated posts.

view more: next ›

falconfetus8

0 post score
0 comment score
joined 2 years ago