• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 4th, 2025

help-circle

  • It’s intended to be a successor to the current reCAPTCHA, sold as harder to spoof than current picture-based versions. Now, almost from its start, CAPTCHA existed to train AI vision models. So Google basically painted themselves into a corner using free labor to train models good enough to recognize images, now they are switching to device signals.

    That said, they’re going to have to provide a compatibility layer for iOS which AFAIK doesn’t come with Google Play Services right now. So I have some faith in the smart folks who make these de-shittified OSes working something out via microG or the like.




  • This is fundamentally not how Signal works, but you are generally correct in that a phone number has been shown to provide a lot of context for a person (or a device, at least). But Signal (the app) only uses a phone number for initial verification of an account. You have a lot of options to break that association with you - use a landline and get a call verification code, use a VoIP number (assuming you trust the provider), use a burner SIM, etc.

    Once you have an account, you can choose to identify yourself on the network solely via username so the registration number is not presented to other users. The Signal protocol itself is well-audited and generally secure.

    If your issue is with Signal the American company, use an open source fork like Molly with your own UnifiedPush instance. Then you’re only trusting them with transport of your encrypted messages, which again have shown to be secure at least in public audits.


  • In the US, I largely agree with you. Or use a website from a mobile browser. Different story in different countries where a smartphone might be the only compute the average person has, or where state services are tied to a mobile ID or bank app.

    Not saying that should be the case, but if the choice is between running niche FOSS apps and removing yourself from societal benefits structures, I know what most people will pick. That’s the real danger of allowing one company to own an entire ecosystem and have enough power that they have conversations directly with governments about their people instead of with their people.






  • 100% it’s always a question of your resources vs theirs, but you’re dead on to make it harder.

    I’ll just add to also turn it off, pull the SIM, and show in a Faraday bag on your way back too. If the recent reporting about ICE buying location data from ad networks shows anything, it’s that they are interested in a capability of following people to and from protests. Graphene should obviate this by disabling Google Play services by default anyway.

    You should leave your regular phone at home, go to another place, power on your other device, speak your part in public, then travel another location and power off. This provides no consistent start or end location to work with for a particular device.


  • Alright, I already “umm, ackshually’d” someone in this thread but this post in particular hit a nerve with me. The Tor security model is based on 3 hops but does not guarantee 3 different jurisdictions. Their circuit building only takes into account “jurisdiction” in the way we’re using it here if you use guard nodes or specific cases when you cannot access the network directly or look like you’re exiting from a Tor node.

    That said, it’s still a very strong project and security model. And everything you said about spreading out your providers without a single point of failure (or pressure) applies.





  • This is a fundamental misunderstanding of how the FIDO2 standard works. It is not designed to be vendor specific and as other people in this thread point out, plenty of open-source secrets managers and hardware implement passkeys.

    What we’ve seen is the typical Silicon Valley model of “embrace, extend, extinguish” so you’re right to be wary of any implementation by Google or Microsoft.

    Same goes for biometrics - how you unlock the passkey isn’t specified in the standard. It is left up to the implementation. If you don’t want to use biometrics, you don’t have to.



  • I think you are overestimating the amount people will pay for convenience or cling to their old ways.

    Did e-readers kill the bookstore? Some people will always prefer to cook out of a book or dive into docs to write code.

    Or look at the modern streaming landscape. In the beginning there was basically Netflix and everyone was fine paying that monthly fee for the convenience of streaming basically everything. Now we have 20+ vendors all charging for some subset of content. And we have seen a corresponding loss in subscribers as people hit the limit of what they are willing to pay for convenience.


  • I’ll play devil’s advocate here: agreed that the rest of the (US) economy seems to be slowing or shrinking but remains buoyed by AI / Mag 7 stocks. That said, a lot of the investment reflected above is in data centers and hardware (Nvidia, Coreweave, Oracle, Microsoft).

    The bubble pop will hinge on whether there is value in this data center buildup beyond AI. Unless everyone starts paying fistfulls of cash for AI chat, these companies may be able to find another use for all that compute and avoid a total crash. That could be a target for all that investment you mention.