They haven't posted weights/inference solutions for LongCat-2.0 [1], but LongCat-Next had transformers support, which I assume means it works with vLLM/SGLang.

Given it's 1.6T, "common hardware" is probably out of the question; even 2bpw is going to measure out at 400GB, even before considering the bandwidth requirements for 48B active. I haven't read the LongCat-2.0 architecture docs, but if you're not running GLM-5.2, you're probably not running this either.

[1] https://huggingface.co/meituan-longcat/LongCat-2.0: "Model weights coming soon — stay tuned!"

Interestingly, it seems like you weren't joking about the decline:

> Finally in the spring of 2022, a sanction reform referendum succeeded with more than 80% of the vote, changing the penalty for an Honor violation from expulsion to a two semester suspension. [1]

[1] https://en.wikipedia.org/wiki/Honor_system_at_the_University...

was the giveaway for me

So, it technically didn't change the secret word so much as it was trying to infer what its own secret word might have been, based on your guesses.

There is probably more nuance behind that decision than I’m giving them credit for, but from a technical standpoint it’s just a checkbox.

[1] https://dev.epicgames.com/docs/game-services/anti-cheat/usin...

Then again, I'd also assume Cloudflare just de facto hellbans all Tor exit node IPs, so...

You'll be flagged as a bot if your browser configuration has something "weird" (e.g. webrtc is disabled to reduce your attack surface) and you will be completely unable to access any site behind cloudflare with the anti-bot options turned on. You'll get an infinite redirect loop, not a button to click.

https://godbolt.org/z/qxsKWfz9s

https://searchfox.org/mozilla-central/source/toolkit/xre/dll...

sshd_config requires root to modify, so you've got bigger problems than weak passwords at this point.

> The narrative that you just told me [about utility shopping] is “I am a very analytical person who only has book smarts and no emotions”. And that narrative is boring!

> It should be noted that the scope of the code reviewed within this audit is relatively narrow. In particular, while we audited cURL’s use of the third-party libraries ngtcp2, nghttp3, quiche, and msh3 to implement HTTP/3 functionality, we did not investigate the internals of those libraries—which is where the majority of the low-level parsing and data transformation necessitated by the HTTP/3 protocol occurs.

the report goes on to concede

> [we] did not observe any coverage of the nghttp3 library code. We suspect that, as the HTTP/3 protocol itself is significantly intertwined with TLS, the encryption makes it hard for a fuzzer to progress to the point where data can be decoded and parsed meaningfully.

[1] https://curl.se/docs/audit/trail-of-bits-http3-report.pdf

> The target iOS device receives a message via the iMessage service, with an attachment containing an exploit.

and that one of the effects of Lockdown Mode is

> Messages - Most message attachment types are blocked, other than certain images, video, and audio. Some features, such as links and link previews, are unavailable.

It might be prevented. Pretty sure disabling iMessage altogether sidesteps this class of bugs too. I've lost track of how many times iMessage has been the root cause of "unattended iOS RCE," at this point it's almost user negligence to have left on.

FWIW, I had the same thing happen and found out the ban reason was "fraud (please insert phone number)".

[1] e.g. for email: https://www.etsi.org/deliver/etsi_ts/102200_102299/10223202/... - the specs are really boring to read and there are lots and lots of them, if you want to deep dive. From what I can tell it's basically just the service provider implementing an API client that feeds everything they're required to a centralized endpoint.

Is it really "in force" when, despite much ado, no charges were brought in the linked scandal [1][2]? I don't really have a horse in this race, I just took issue with the particular example you referenced.

[1] https://www.nytimes.com/2020/05/26/us/politics/senators-stoc...

[2] https://www.cnbc.com/2021/01/19/doj-will-not-charge-sen-rich...

I’m guessing they’re intentionally degrading the non-Javascript page as an anti-bot measure, but it’s so bad that I find it disingenuous to suggest that the non-Javascript page even a valid alternative at this point.

[1] https://en.wikipedia.org/wiki/Common_Address_Redundancy_Prot...