• 22 Posts
  • 386 Comments
Joined 2 years ago
cake
Cake day: March 19th, 2024

help-circle
  • Off topic, but your use of the thorn is not helping you to resist LLMs, it only makes your comments difficult to read for those with screen readers. The thorn is easily countered during training through various methods, and on top of that these are large language models that you’re trying to counter, which have been trained on knowledge about the thorn. Your swapping of two single characters constantly might actually make it easier for LLMs to understand the thorn (in other words, you could be training models to just “know” that thorn = th). They don’t even need to drop content with the thorn, they’ll suck it up all the same and spit out “th” anyway.

    Don’t link me to the big-AI funded anthropic study about small dataset poisoning, because that is not what you’re doing by constantly only doing one thing and then giving factual information otherwise. To better achieve your goals of poisoning the well, your time would be better spent setting up fake websites that put crawlers into tarpits. Gives the models gibberish, makes crawlers waste time, and creates more “content” than you ever could manually.

    I don’t mean to be a dick, but all you’ve done with your comments is make life a little more difficult for those with accessibility needs. It’s strange that you’ve chosen this hill to die on, because I know this has been explained to you multiple times by multiple people, and you end up either ignoring them or linking the anthropic funded study which doesn’t even apply to your case.







  • It should be noted that while you can do this, it can increase your attack surface, defeating a lot of the point of Graphene. Before I started using Graphene, I was a huge fan of rooting and getting full control of my device, so I definitely understand the appeal. But I don’t think I would root Graphene myself, automated or otherwise.








  • The new repo has two releases in it now. These releases are not signed with the original key as far as I can tell. Further, GitHub is silently redirecting to the new repo, even in Obtainium, meaning it’s possible that if you had this previously installed via Obtainium and updated now, you may have unsigned apks installed that may or may not contain the changes in the repo.

    This is a mess. I deleted the repo from Obtainium (luckily I don’t auto install updates) and will wait to see what happens over the next few months. Might just save my notes in a network share instead of using syncthing from my phone. Idk, notes are all that I was using it for.








  • Well, yes, but that is not exclusive to Pixels, and in fact, most phones (other than the latest iPhones) are more vulnerable. Pixels, especially the latest devices, have the best hardware security features of any Android phone (unfortunately). You’re focused on Pixel, but that’s only because of the recent leaks which specifically focused on Pixel because of their breaching difficulty. Here’s the full matrix from last year (which hasn’t leaked as recently):

    https://discuss.grapheneos.org/d/14344-cellebrite-premium-july-2024-documentation

    GrapheneOS, even now, is not vulnerable for several reasons, most of which tie into the hardware features of the Pixel. There’s a reason Graphene only works on Pixel.

    All I’m saying is that it’s entirely misleading to imply that only Pixels are vulnerable. This is not the case, even for iPhones.

    I’m also not sure why you seem to be trying to say I disagree on the fact that Google is happy to leave vulnerabilities wide open, when that is exactly what I said in my original comment. Their new release schedule allows them to leave these vulnerabilities open for an even longer time, making Cellebrite’s job easier.