National Guard listens to the state by default, as each state has its own National Guard. However, the federal government can intervene at any time and give them new orders.
I guess they’re just choosing not to do anything? IDK.
National Guard listens to the state by default, as each state has its own National Guard. However, the federal government can intervene at any time and give them new orders.
I guess they’re just choosing not to do anything? IDK.
Lemmy’s mobile UI is nice. Voyager is just a PWA, and it’s both really smooth and stupidly nice. In my eyes, the spiritual successor of Apollo. I’m not leaving it.
What’s with the big and blue username?
From the README:
Feel free to take a look around. We are not yet taking patches as we still have a little bit of tidying up to do. When we do, there will be a contributor license agreement.
So yeah, looks like there will be a CLA.
I blocked most news communities. Stuff slips through, but I don’t really have the mental capacity to care about it.
Use an app? I use Voyager and it’s a really smooth experience, and I haven’t re-logged in since I first got it.
Public transport.
This post isn’t on Lemmy.world.
That’s the point of a hash function. You have a public hash function, say SHA-256. It’s easy to check a username against it’s hash, but virtually impossible to reverse the hash back to the username.
Edit:
Instead of storing, say, eddie
, we’d store 3b9d8298f1b5086d012618feebb2da1a394357c1dab7523443c9f6a743c4c84d
. Then when the instance gets a Like
from eddie
, it hashes his username to get 3b9d8298f1b5086d012618feebb2da1a394357c1dab7523443c9f6a743c4c84d
, realizes there’s a match, and doesn’t update the count.
Note that when given 3b9d8298f1b5086d012618feebb2da1a394357c1dab7523443c9f6a743c4c84d
, it would take millions of CPU years to compute the original username from it. Therefore, we can check for duplicates without actually checking the name itself (a similar method is used for checking passwords; Lemmy is open source, we know the hashing algorithm, but we can’t unhash user passwords, only check them).
Couldn’t we just use a hash for the usernames instead?
Nothing too over the top, but just a simple hash and match that instead?
Also, there’s way too much trust in instances. Like, one person could easily make a post on lemmy.world, go on their personal instance, and just give themselves, say, 2000 upvotes.
Instances should have their own settings on what instances are allowed to keep a local copy. (Default behavior should be to get the post itself from the instance “hosting” it).
Honestly, this is why I’m hoping the Vsuon Pro doesn’t flop. It really feels like it could open the door to a new era. Of course, that’s still years away, but you’ve got to start somewhere. Better now than never.