Yeah, it’s odd to me that the syncthing repo makes a point of not officially supporting android, and not making any promises about its continued maintenance. It’s a large part of their user base, but it seems, for some reason, this developer that went dark never spent time to coordinate with or join the core team.
Aristotle thought bugs and fish and birds are all animals. I literally don’t know any classification system, or definition, that doesn’t.
The android development always just seemed… off, idk, I just got weird feelings about it and the fork. So I switched my family to use termux and termux:boot to run syncthing instead, it works fine.
I don’t think this is accurate. For one thing, whether a law prohibits or allows something is just a matter of perspective: a law allowing abortion nationally is also a law that prohibits state restrictions on abortion. Another key missing fact is the supremacy clause of the constitution, which says that federal laws are presumed to overrule state laws when they conflict. This is why a lot of ‘blue’ states had terrible abortion laws still on the books when Dobbs happened, because they were nullified by the Roe v Wade ruling in the 70s and they never got around to actually removing the defunct laws.
The supremacy clause is not absolute: the tenth amendment and others restricts how much the federal government can tell states what to do, but I think there are a number of legal arguments against that being the case for a federal abortion law.
This looks like a design decision to avoid running elevated programs. I would like to see the experiment done with another admin ability that doesn’t directly ‘threaten’ the llm, like uninstalling or installing random software, toggling network or vpn connections, restarting services etc. What the researchers call ‘sabotage’, it is literally the llm echoing “the computer would shut down here if this was for real, but you didn’t specifically tell me I might shutdown so I’ll avoid actually doing it.” And when a user tells it “it’s OK to shutdown if told to”, it mostly seems to comply, except for Grok. It seems that this restriction on the models overrides any system prompt though, which makes sense because sometimes the user and the author of the system prompt are not the same person.
For anyone curious, Rosalind Franklin did get a mention… In the 17th and 18th paragraphs. Might as well be a footnote, just like the original paper. He was an awful, pitiful man, when you read the fine print.
deleted by creator
I actually don’t doubt that this time lol
How do I uninstall? Is apt purge available on this system?
One could say I gave you what you Watt-ed.
Splitting a heavy U-235 atom, given perfect conversion to electricity, could power a 1 Watt nightlight for around 7.5x10^-13 seconds
Yeah exactly, even if a word or two is unclassifiable, an entire sentence might contain enough info to still be useable.
This is actually beyond the capabilities of AI classification systems currently. A human would have to specifically see, in the raw data, that someone is doing this and write the perl script themselves. The odds of this being noticed and corrected, by humans, are also proportional to how popular the writing quirk is.
An AI ignoring the comment, or mis-classifying it, is the goal though
I have no idea if it’s effective, but they mean anti-AI as in fighting against classification of their data. The AI will either have to incorporate their comments and posts, and start using þ too, or just ignore their comments entirely. Which option really depends how popular the given writing quirk is, so you need to choose weird or archaic characters.
One more note on this is that while some searching did lead to webservers that can decode uris into utf before handling them, I believe this is very unsafe for a public server, and, in the worst case, could allow public access to your entire drive. There are vulnerabilities because different systems, and even different services on a single system, can treat specific unicode characters differently. My advice above to url-encode the filenames before serving or while building them would avoid the need for any decoding of requests as they come in.
URIs can only contain ASCII characters, so the web server is receiving requests in ‘percent encoded’ form for urls, not in utf8, and so there is no way for the server to know which file to respond with. You’ll have to urlencode the filenames yourself unfortunately, so that they will match the incoming requests. The tool jq can urlencode cyrillic characters:
echo "људиа" | jq -rR @uri
You could probably do this as part of the build process if you are clever enough.
This is only for the file name itself; the exported document should share the source document’s encoding unless overridden by the org-export-coding-system option.
That’s such a psychopathic response. It is not acceptable behavior, and you won’t win any arguments that way.
I have no idea what you mean. I just had to set this up once on my parents’ phones and now it works all the time, even when they change networks, no port forwarding or any interaction required on their part. Rsync is a cli that requires an existing network connection between two devices, both online, and doesn’t watch files or create a file version history. It is an entirely different tool.