Ok this is actually a great point, and I’d like to pose another question. If you’re gonna pee standing up with the lid open, what’s the optimal angle to minimize splatter? I would love to see an experiment or simulation to find the optimal angle.

I have. Men with bad aim. Skill issue.

One possible fix is adding a urinal target. I’m sure you could implement a similar concept in a regular toilet.

A urinal target, sometimes known by the specific types urinal fly or urinal bee, is an image or mark placed inside a urinal to encourage users to aim in a particular place so as to avoid messes and reduce cleaning costs.

This is a shit take literally. Why would I sit down to pee if I don’t have to? That’s more contact with the gross toilet.

Yes! There would be a spec written for blocklists that could be applied to Lemmy or PoeFed. You can quickly toggle on/off a blocklist. For example, I can subscribe to a “US Politics” blocklist, and toggle it on/off when I need a break from news.

People don’t understand PieFed. It’s a fantastic project, but if you think switching to newer price of software that is still under development is going to have less hiccups…. Well you clearly don’t know how software works. This is not a knock on PieFed. On the contrary, I love what they built, but you have to have patience. This is free software build and hosted by volunteers. OPs just gonna wind up complaint that PieFed also has hiccups.

It’s kinda mildly infuriating that this is mildly infuriating. Lemmy and PieFed are free, open source software run by dedicated volunteers. Many of those volunteers spend quite a bit of time making sure everything runs smoothly. Hiccups are gonna happen. You should donate to your instance if you wanna help things run smoother in the future.

I thought Elon was doing his own party now. Who is “us”?

Web 1.0 was great. Why Web 2.0?

Blorp dev here. I also had this idea awhile back that I never built, but basically some preset blocklist you could subscribe to. Sick of US politics? You could just toggle on the US politics blocklist instead of manually adding your own terms, communities, etc. Just an idea, but I’m curious if that appeals to anyone.

Blorp dev here. I’m trying to decide what settings to support. Blorp is both PieFed and Lemmy, and supporting all features from both could get really complicated. So I’m starting simple and I’m going to add the features that get requested the most.

Edit: also forgot to mention iOS will reject Blorp form the app store if it has a “NSFW” toggle, but there is no reason I can’t add that to Blorp when distributed outside the App Store.

Ok, hot take, you can’t judge the bread as a slice by itself. It’s the context around the slice that matters. For example, dry foods can be good when paired with non dry foods. But on their own, I’m not a fan of dry foods. I can see the end of the loaf being good when paired with the right filling. But in the context of a slice of buttered toast, I don’t really want the end of the loaf.

Now that’s a spicy take

Indian food. That picture looks delicious!

Is that toilet paper?

Yes. I’m not sure if it’s a good or bad habit

I wonder how that works. The point of password hashing is to uniquely scramble your password. So userOneHash(“password”) should give a different output than userTwoHash(“password”) even if they use the same password. So your password manager shouldn’t really be able to generate the same password hash since an infinite number of hashes can be generated from the same password.

Can you also use a list of common passwords and a ruleset you apply to those common passwords, and then hash(applyRule(commonPassword), salt) == compromised hash ?

I actually didn’t realize pepper was a thing. I mostly do frontend. But that’s really interesting!

But if you use a salt that is global to your site/server, you still have this problem: If a hacker cracks “p@ssword” in your database, they immediately know all users that also use “p@ssword”. Imo the biggest benefit of using salts is two users with the same password get different hashes. Right?

I’m not saying using a global salt isn’t better than no salt, but I do think you’re missing out on a huge benefit of using a per hash salt. Keep in mind I’m a frontend engineer not backend or security lol.

even if someone brute forces an offline copy of the hashes they wouldn’t result in actual useable passwords

I thought you were suggesting that salted hashed passwords were uncrackable but maybe I misunderstood this

Edit: I understand the offline pepper part now. My bad