I didn’t say I wanted to lurk. I’m just saying I find beehaw’s Technology community more to my preference than LW’s

There’s plenty of communities where I have no interest in discussing things with the masses. I like smaller communities with thoughtful posters who care more about the subject matter than being heard. That’s the beauty of Lemmy. Not everything has to be perfect for everyone.

What’s so good about PieFed?

They’re still cosplaying decentralisation. Google hosts images on a separate domain to the one where they serve documents, are they decentralised? When we see more indexers, by all means let’s consider BlueSky decentralised, but until then, they’re just offloading traffic.

It’s adding centralisation where there’s no need for any. In the same way that BlueSky cosplays as decentralized, this is what this effectively tries to move towards. In that whoever runs the relays/indexers is in control.

Of course mastodon wanna power grab

I hear you, but it features Mastodon very prominently and Mastodon aren’t exactly reputable for supporting anything. Going as far as to implement things in a manner that breaks compatibility with other Fediverse services.

The absence of any Lemmy mention seems weird to me.

Didn’t she just have a baby?

Loved the branding and was so hopeful, but like everyone else, I long thought the project was dead.

I like it

1. Matrix has nothing to do with the Fediverse.
2. Given that they’ll regularly push updates of Element to the Play Store without tagging releases on their repository, effectively leaving F-Droid users without releases and with a clogged up Play Store, I’m unsure why you’re surprised at the lack of sense of duty to users.
3. There is no real three.

Someone posted something recently that checked a bunch of functionality across different networks.

Exactly! To say it’s very right wing would be an understatement.

Yup. Pretty much the same thing but on a different network.

That’s a Nostr relay, nothing to do with the Fediverse.

Just add a function so when you change your profile, it also pulls all records that match md5(userid, password) and then update them records too.

Though I’m convinced the overarching logic is correct, this is not my wheelhouse, so I’m probably wrong.

Dammit! Okay, cancel the salt idea. How about just a simple md5() and then it should remain a static value right?

@dullbananas@lemmy.ca does the design hold up?

So I’ve been thinking about this and I would go for a different approach.

Admins can set voting to be public or private on a server wide level.

When users vote, a key is created as the userid

The votes table is essentially: voteid, postid, userid, timestamp, salt, public

If the vote is private, userid is salt(userid, password)

And it’s that simple.