

But only the toilet has an open hole in the middle for your butt to hang down through, and you’re usually not spending any time trying to push out a turd on any seat that’s not a toilet.


But only the toilet has an open hole in the middle for your butt to hang down through, and you’re usually not spending any time trying to push out a turd on any seat that’s not a toilet.


could just be plain old ear muffs, for noise reduction.


took me too long to figure out to read it as re-styling rather than resty-ling.


I replaced Pixel launcher with Lawnchair. Very similar UX but let’s you do things like set the search bar to just open your default browser.


could you not just get a data-only SIM?
The sun set earlier,
It didn’t. You just go up earlier and pretended.
We did year round DST in the 70s and it resulted in kids being hit by cars on the way to school in the winter.
Heart attacks and strokes are more frequent after DST starts
No they enacted permanent DST in the 70s. OP is asking for arguments against ending DST. The backlash against permanent DST in the 70s was because kids going to school in the early morning darkness were being hit y cars.
We already tried year-round DST in the 70s. It didn’t last through the first year because kids were getting hit by cars on the way to school in the early morning darkness.


If it’s open source it can be verified that it’s not storing the data.
And I 100% agree that software scanning an ID is an overall bad way to verify. With a CC# validation at least that shows up on my statement, but if my kid is sneaky enough to get mine out of my wallet I have no way of knowing.


I feel like #1 and #2 are problems whether its client side or server side. As for #3 I would lean in the direction of there being a one-time check with no persistent knowledge. Like when you flash your ID to the bartender to order a drink. A client app that scans the ID and returns the answer to the requestor.
But I don’t think there is any way to reliably implement this sort of thing. I think it should really just be left to parental control and monitoring.


Some kind of cryptographic signing of the executable could probably help with that.
Ultimately I don’t believe there can ever be a foolproof solution and the emphasis should be on client-side parental controls.


This goes in a better direction than web sites doing it themselves, I think. The government put out an open source tool that runs locally and the browser just gets a yay/nay return code from it.


I just bought a few WD drives direct, but their web site has a problem with validating virtual credit card numbers. I’m the few days it took to resolve it the price went up. Fortunately since I had the support ticket I was able to get refunded the difference.


What if it was just an off the cuff joke?


You know Russ, I’ve been known to fuck myself.


I guess you’re not thinking of “locked down” in terms of independent developers finding the iOS and Android “play by our rules and be distributed thru our app store or we’ll make it hard for users to run your software” to be a barrier to distribution.


I was referring to this
If this technology is successful, the end result could be that we would see our Linux laptops one day being as locked down as an Iphone or Android device.
There’s nothing as permanent as a temporary fix.