I am not party to all the information, but he was never charged for the alleged misconduct and Die Zeit’s investigation didn’t find it convincing. Given how the Assange allegations fell apart, I think there’s a non-zero possibility that it was a defamation campaign.
He didn’t help himself with some public conduct/comments that painted him unfavorably. So there is that aspect to consider. But the scope of the campaign against him felt excessive at the time, to me.
One of the accusers refused to sign their written statement, then disappeared. The other kept making contradictory statements and changed her story, and recently said she was “happy” that he was free, although she did not recant her accusation. Prosecutors also allegedly changed one of the statements to make it sound more serious, per the later UN investigation.
They put out an Interpol notice and had him on the “most wanted” list for this, which is ridiculous. There is documented communication between the UK’s Crown Prosecution Service and Swedish authorities where the CPS is goading the Swedes into continuing the case, warning them not to get “cold feet.”
The prosecution eventually dropped the case because they believed that the evidence was too weak, blaming the long gap in time. I’m not clear on how they thought the passage of time had weakened their evidence, which was limited to victim statements from the very beginning, AFAIK.
A longish life has taught me to believe vulerable women who open themselves to ridicule, mistreatment and attack for outing more-powerful men who harmed them.
The women who outed Jason Applebaum knowingly opened themselves to some harsh treatment. I believe them.
>A longish life has taught me to believe vulerable women who open themselves to ridicule, mistreatment and attack for outing more-powerful men who harmed them.
A longish life has taught me to cast a very skeptical eye on anyone who comes out of the woodwork to cast evidence-free allegations on people who have raised the ire of the entire "national security" establishment.
Many believed the women who accused Assange of rape also that led to the bogus charges that had him imprisoned in an Embassy and then a British dungeon for years.
>who craft no end of reasons to not believe them.
The reason is that these allegations surfaced after he aroused the ire of the national security state. That's the end of the reason.
Has it been settled whether robots.txt applies to user-driven chat sessions and if things like the crawl delay should be applied to say an end-user, an ip address, a harness provider, etc? My understanding is robots.txt is more for training exclusions, but less so for agent work.
robots.txt was only intended to help search index crawlers not get stuck in endless crawl loops for badly designed websites.
What you suggest is explicitly not a purpose of robots.txt per RFC9309[1]:
"These rules are not a form of access authorization."
HTTP 429 and HTTP 403 are what servers are meant to return to clients to slow them down or tell them to stop doing something without having first gained authorisation.
robots.txt applies (or should, in my opinion) to anything that automatically follows a link. Basically any software that is not a human-controlled web browser or single-shot curl command. Everything else: robot.
AI bros think they should be exempt from robots.txt. Administrators of big services beg to differ. No solid consensus has arisen. I bet it's gonna take a lawsuit or two to see how it shakes out.
wget ignores robots.txt outside of recursive mode. I think it's correct to do so, and I think an AI loading a handful of pages in response to a command should be about the same.
If a new directive was introduced that allows for an explicit setting in robots.txt, do you think the bros would follow it anyway? Something like `ALLOW AGENTS` or `DISALLOW AGENTS`
I wouldn't want them to. The whole point of using agents to do stuff on the web for me, is for them to do the stuff on the web for me.
This is the reverse of "do not track" case. It'll not be effective because every service will set it to DISALLOW by default anyway, because it costs them nothing, and for most services, it actually is what they want anyway - most of businesses on the web are making money on wasting people's time, and for that, they need to force themselves on people; end-user automation defeats that, so they actively fight it (and complain a lot).
> Yes. Grab those open-weight models while you still can.
You mean like it's impossible to download a movie because it's illegal, it's going to be impossible to download open-weight models because it's going to be made illegal?
So for the same definition of "impossible", it's going to be "impossible" to download open-weight models?
> And to clarify, this means encrypt it before it gets to the VPS. Just having full-disk encryption is not enough because cloud providers can dump RAM. There are tools that easily extract encryption keys from RAM.
True, but at the very least, you won't have to worry about discarded SSDs having your data in plaintext.
If you carefully re-read what GP wrote, you'll see there's no reference to Earth's orbit or 1 AU in there. GP wrote about the solar wind scattering cosmic rays when it reached some point in its outward travel.
Check out other comment. It could actually end up causing more warming in the long term depending on the net change in fuel use or extra maintenance on plane etc.
The required changes are typically minimal. A little bit of altitude up or down, a minimal detour. Also mentioned in other comments (and in the article).
I think this is a good practice anyway. Putting as much code as possible into silos with guarded permissions.
Historically plugins have been kind of crappy because they were constantly breaking with updates. However if they only live as a spec, and are regenerated when needed they can easily survive API changes.
Bonus feature is that if all “installed” plugins are generated together, the llm can also find ways to avoid them being buggy due to weird interactions.
All this while keeping the main program from crashing.
Security wise the spec can also be inspected using a trusted LLM. It is trivial to hide exfiltration or malicious code in plugin/extension code (e.g.: honey). But it is much harder to hide it in a spec.
reply