• 0 Posts
  • 153 Comments
Joined 3 years ago
cake
Cake day: October 5th, 2023

help-circle
  • There’s plenty of long form AI content lately too. Wikipedia articles make for great YouTube videos, and there’s no shortage of them. I’ve run into several channels lately where it took me about 30 seconds to realize something was off, and checking the channel’s history you can usually tell by finding older videos which actually have a person in them who is clearly very different than the narrator in the newer videos, or by just not having any older videos at all.


  • My controversial opinion is that if he’d never run in the first place and made sure Harris played a significant role in his administration, she could have had a shot at winning it with a full campaign. If she were a white male it would have maybe even been easy. The Democrats will never run a truly progressive candidate, and as proven in Kentucky this week the over 60 voting block still matters most.

    And yes, if you can’t tell I have absolutely no hope for US politics. But I’ll still at least vote for whoever isn’t the fascist every time.





  • I highly doubt any power users will move to IOS. IOS is far more limiting than even a locked down Android. Graphene is a far more likely candidate, though I suspect most will just stick to normal Android with unverified apps enabled as they have their phones configured today. This change is really just an added 24hr delay to the existing process of enabling unverified app installation. If Google had just announced it this way I suspect there wouldn’t have been so much pushback. But instead it was rumored that unverified installation would only allowed over adb which would absolutely be too much friction with little security benefit.


  • They’ve recently announced the flow to enable unverified apps. It’s a one time process which will require waiting 24hr after enabling unverified apps but after that 24hr installing APKs will work exactly the same as today. It’s annoying Google has single-handedly decided to implement this rather than going through a more transparent method built into AOSP, but if this is as far as they take it I doubt any power users will be seriously impacted. Of course with how Google has handled this I have no confidence that this is as far as they’ll take it.


  • If this is really as straightforward as it sounds then I’d consider this the best case scenario. Google could have gone full Apple style lockdown or even just have implemented this flow on a per app basis, but needing to wait 24hr one time to enable unverified app installation isn’t a bad idea from a security perspective. It prevents a bad actor with temporary access from being able to do much while not getting in the way of us power users after the initial 24hr period.

    My bigger problem is how Google is leveraging their monopoly to implement this single-handedly and only for themselves. If they had instead gone through AOSP this perhaps could have been implemented in a better way to allow other parties than just Google to be the verifier, and that 24hr waiting period could be applied to any verifier that is not the phone’s default. I’d argue this would be an equally reasonable security measure considering how many scams are out there preying on those who aren’t technologically savvy, yet would maintain transparency.



  • These attacks are more around the encryption and all require a fully malicious server. It sounds like Bitwarden is taking these seriously and personally I’d still strongly prefer it to any closed source solution where there could be many more unknown but undiscovered security concerns.

    Using a local solution is always most secure, but imo you should first ask yourself if you trust your own security practices and whether you have sufficient hardware redundancy to be actually better. I managed to lose the private key to some Bitcoin about a decade ago due to trying to be clever with encryption and local redundant copies.

    Further, with the prevalence of 2FA even if their server was somehow fully compromised as long as you use a different authenticator app than Bitwarden you’re not at major risk anyways. With how poorly the average person manages their password security this hurdle alone is likely enough to stop all but attacks targeted specifically at you as an individual.





  • I’ve used these in San Francisco and Colorado Springs. You press a button to open the door, then once inside another button to lock it. You then have up to 5 minutes to do your business before the door will open again iirc. Toilet paper is carefully rationed out and dispensed. Once you are done and leave the door will close behind you and sprayers pop out pretty much everywhere, washing down every single surface. Sometimes the toilet also folds up for a more thorough cleaning of the seat. This means they’re always a little wet inside, but also remarkably clean. SF in particular really impressed me with these, I expected them to be absolutely disgusting and tried my best to avoid them until I had no choice. The US needs public toilets, and assuming the maintenance costs are low enough the self cleaning ones really aren’t as bad as an unattended public toilet sounds on the surface.