Huh, we still almost always have SMS as a validation method for 2FA here, so any SMS to web method works.

ah, two factor authentication is the issue then?

For all of those following, I emailed Rob and he confirmed that the focus of the project to start is reverse engineering binary blobs on existing android devices, but he is currently only at the discovery phase of picking which phones to start with. He is first checking LineageOS compatible phones using his toolset here: https://codeberg.org/rsavoye/librephone/src/branch/main/doc/index.md

Huh, they still work for all my banks here in the US. Not sure how you’re supposed to access your bank account on your PC otherwise. Some banks you’ll have to use the “use Desktop version of the site” option in a mobile browser to get it to work, but it will still work.

It isn’t encouraging that they “launched” the initiative bit have no dedicated webpage or git for it yet. Seems like going off half-cocked

This is the entire goal of Palantir, presictive policing using mass surveillance data on citizens. Tie in digital ID and you have an even worse version of the CCP’s Social Credit system.

The project just launched and is a software-first project. We won’t see a Libre Phone available for a while yet.

Excellent article! The invention of clean room procedures for environmental testing probably exceed even his successful campaign to ban lead in gasoline as far as positive impact on society. Clair Patterson is a true hero of science.

It’s all just supper after all.

Killdozer 2: Super-Killdozer, the Wreckoning

Dangit, forgot to lead with TIL, ah well

(the best) Local LLMs are FOSS though, if bias is introduced it can be detected and the user base can shift away to another version, unlike centralized cloud LLMs that are private silos.

I also don’t think LLMs of any kind will fully replace search engines, but I do think they will be one of a suite of ML tools that will enable running efficient local (or distributed) indexing and search of the web.

You’re joking right? “making up answers” in the case of search results just means a dead link. If you get a good link 99% of the time and don’t have to use an enshitified service, that’s good enough for 99% of people. Try again is the worst case scenario.

Also, you know what would make this all even worse? Laws requiring that people prove their identity in order to consume content or pull videos… just like age verification laws now being passed in several countries. What a coincidence.

Not to mention that the scraped indexes can and should be shared. Unfortunately what OP is seeing may be a move to thwart this type of brute force scraping, and might resolve as dynamically assigned domain addresses, where the URL of a set object is temporarily assigned and streamed only to a single or group of IP addresses that request it within a given timeframe before being rotated out until found in search again and then reassigned a new URL, etc. This is a frankly stupid use of resources, but can effectively be used to prevent crowdsourced indexes from proliferating, and to punish IPs or even MAC addresses or browser fingerprints associated with downloading and reuploading videos which almost certainly have stegnographic fingerprinting embedded that associate with who the video was served up to at the time it was downloaded.

That’s fair

I looked around a bit more, seems to be regional which is growing faster. UK Meshcore is growing fast, which makes sense since core devs are there. I haven’t found a good statistics source for node numbers, probably for the best given the network goals. Meshtastic of course is older so has the inertia lead, but the security and routing of Meshcore definitely is appealing to me and seems better for emergency situations where text messaging reliability is top priority.

Meshcore is currently considered superior in most respects to Meshtastic, and as a result has a faster growing user base.

https://meshcore.co.uk/

Windat

If only I were the king of the world!

I think what you are arguing for is hardcoding requitement for signatures with an “age appropriateness” ranking into the OS. How does this change the current situation where adult sites and apps are legally required to have an age verification popup/warning? Whether signature based or graphically based, what is at issue here is age verification which means referring to some “repository of truth” outside the will of the user. The problem is that the effect of this is to link government ID directly to web traffick, as to truly verify age requires verifying identity meaning abolishing anonymity on the web and enabling complete tracking of dissent.

I could see a version of what you are describing akin to the way physical cryptographic keys are used to manage DRM on high end enterprise software, where identity/age verification would need to be done by the hardware vendor and not the software/site, the problem with that however is the aftermarket and multiple-user devices. You could say that the “age key” would be a hardware device sold to adults using physical ID akin to spirits or tobacco, something like a SIM Card but preferably with NFC rather than having to be installed in the device. “Adult Access” would then be enabled on sign-in by scanning the “age key”, enabling onboard software to serve software and sites that don’t have an “all ages signature”.

Honestly as I write this, it isn’t the worst solution, the main thing would be keeping the Age Key as an interchangeable, replaceable device that only interacts with the OS and isn’t referenced by other software, so it doesnt just become another Digital ID proxie.