The way that it would make sense for age verification is if there was some federal system that verifies your identity and then it would use a public key crypto system to allow a third party to check whether or not this person is over the age or not.... common systems I see being used right now that could be integrated for this purpose would be login.gov or id.me... they could allow a token-based authentication system for verification of age without having to divulge any other information about the person. these systems are already being used by the IRS, VA, SSA and other Federal systems.
Google has zero customer service. using them for anything serious makes no business sense. the only thing that they're good for is serving ads to people, and they have a support team for that, but only if you're spending a lot of money, and even then good luck finding it
yeah exactly have you ever tried to call Google support? it doesn't exist. the only way to contact Google is by posting something on news.ycombinator.com and then hoping that some person who works at that company actually responds to you and logs in somewhere and then changes your access.
this is the long-standing problem with using Google services. either they become deprecated and removed without notification, or they outright ban you for using tools as intended. either way, using Google tools for anything doesn't make business sense to anybody who's seen the history of this.
the government should not be using any private LLM, they should build their own internal systems using publicly available LLM's, which change frequently anyway. I don't see why they would put their trust in a third party like that. This back and forth about "ethics" is a bunch of nonsense, and can be solved simply by going for a custom solution which would probably be orders of magnitude cheaper in the long run. The most expensive part is the GPU's used for inference, which can be produced in silicon [1].
to avoid these conditions i have usually inserted a row into a lock table used for this purpose to create a lock with a unique key for that row with a few minute timer, the once the transaction is complete it will delete the lock row. This way, simultaneous users will only get the first lock, all other requests would fail, and then if the timer expired, we would assume the transaction never completed and it could try again after a few minutes
if anybody believes that Facebook would allow people to send a totally encrypted message to somebody, they're out of their mind. they're pretty much in bed with law enforcement at this point. I mean I don't know how many people have been killed in Saudi Arabia this year for writing Facebook messages to each other that were against what the government wanted but it's probably a large number.
This reads like another low effort conspiratorial comment.
WhatsApp has been reverse engineered extensively, they worked with Moxie's team to implement the same protocol as Signal, and you can freely inspect the client binaries yourself!
If you're confident this is the case, you should provide a comment with actual technical substance backing your claims.
reply