xena

This is the best news I've heard all week. Finally good news for once!

For what it's worth, Anubis supports LibreJS: https://github.com/TecharoHQ/anubis/blob/main/web/build.sh#L...

The meta refresh challenge actually uses time as the proof! It makes sure you wait for at least 75% of the time the administrator configured and adds client side smear to ensure that browser temporal randomization doesn't trigger a false failure.

Please share with the class :)

That's the only theory we have that doesn't sound like a conspiracy theory. The only other credible ideas are that someone's doing some kind of dataset arbitrage by scraping the fuck out of everything and selling companies data that is technically new (by means of the scrape date being newer).

For what it's worth I'm working on hashx support. It's just going to take a bit to ship while I do browser testing with broken browser configs.

I think this post was written by an AI model.

Things like this make me wish that we have to pass ethics courses to work in tech.

This is AI generated. Why is this being upvoted?

I requested the code for Anubis, I'll keep you all updated on what I get!

IPFS would be much better for something like LFS support than git repos itself. Git repos are very mutable bits of state and IPFS is best for immutable state. I'm aware of mutable IPFS pointers, but I think the best bet currently is to use immutable things for immutable objects and mutable things for mutable objects.

Author of the post here. I'll talk with someone I know at Gitea. I don't think this is viable to upstream into Gitea, but there's only one way to find out!

Author of the article here. I'm aware of ZeroFS and other similar approaches (such as something internal at Tigris that will become public at a later date), this was more of an experiment to see how far you can get with stuff I already had "on the shelf". I am going to be improving this a fair bit; I just need to plan out what I'm gonna work on and figure out the best times to stream it, etc.

It ain't me. I have no connections to Wikipedia and have a "only look, never touch" rule when it comes to interacting with it.

Not unless you get promoted for writing more efficient code.

I filed the bug: https://github.com/llvm/llvm-project/issues/204883

The last time I evaluated doing protein folding it required gigabytes of disk-data to make it happen. If there's a way to do it without needing gigabytes of disk-data, I'm at least interested in hearing it out.

If it's dumb and it works, is it really dumb?

I'm gonna have to file the bug without a minimal reproduction case. The issue seems to be those try_table blocks getting nondeterministically reordered at link time (is it using machine pointers for iteration order?). Sadly I'm observing this with a local checkout of binaryen, so it may take a while for you to find the minimal reproduction case.

I tried doing that at first. I kept running into edge cases that made the whole thing fall to ribbons. I gave up and am just falling back to what I know works: compiling the WASM to JS.

That's great. I love that for you. Please leave me alone.

Surprisingly, cherry-picked examples to prove a point are cherry-picked examples to prove a point.

It's a conscious design choice. Doing that gets you considered a botnet/malware. I don't want Anubis to be considered a botnet/malware.

Anubis is not a cryptocurrency miner: https://anubis.techaro.lol/docs/user/frequently-asked-questi...

Anubis does this: https://anubis.techaro.lol/docs/admin/honeypot/overview

Getting in the maze influences your client's challenge difficulty.

Nix doesn't help when the issue is a compiler bug, sadly.

Patches welcome. I'd love to do protein folding too.

Sadly my initial test case is binaryen which has 290 compilation units. I will try though.

Thank you, this will be very useful.

This might be the first time in my career I have genuinely found a compiler bug. I've been operating under the axiom of "don't assume it's a compiler bug, assume you're fucking it up somehow". When you get to the point that disabling ASLR makes it consistent intra-host I think I've won the right to at least suspect a compiler bug is at play.

I'll go file it upstream after work today.