Show newer
Forest boosted

patient status: deceased
cause of death: [object Object]

Forest boosted

Release the hounds! (The hounds did not want to be released)

Forest boosted

@Tak Yeah in the config, there's a bunch of rules that allow certain things thru, git clients being one of them.

hard to argue with those 3 words : Welcome to nginx!

Forest boosted

Hello, world! We are Bunk Computer Cooperative -- a worker-owned technology #coop in Western North Carolina. We're building local computing infrastructure that's of and for Western #northcarolina

We're still getting off the ground, but we've been hard at work the last eight months and we're ready to introduce ourselves. We wrote an #introduction blog post that you can read at the link in our bio, and we'd be thrilled if you did! Boosts Appreciated!

Yours in bits and bytes,
Bunk Cooperators

@monsieuricon

Right now, I think that these bot deterrents are mostly just functioning similar to a "security thru obscurity" javascript blob.

I don't think the difficulty actually matters at all, you might as well set it to one because if scrapers ever try to solve the proof of work in the future, I think sha256 is categorically not going to work anymore since it's so easy to accelerate and so many accelerators for it already exist (bitcoin).

I actually created a proof of work bot deterrent before the LLM hype even existed. Back then I chose Scrypt as a memory-hard hash function because I wanted it to be as easy as possible for normal website visitors to solve, but as painful as possible for scrapers, even after they perceive it and react to it.

I don't have mine triggering on browser user agents. I just have it trigger all the time by default except for some tools that I allow list like git, npm, go, etc. I also explicitly allow home pages and repository home pages so that search indexers can still find things and display them.

You can see a demo of it here as well as the source code:

git.sequentialread.com/forest/

Forest boosted

@gitea lol jesus christ, people's deployments of their forges are being ddosed constantly by llms nicking their shit, and you're leaning into ai?? read the room

Forest boosted

today I set all the git repositories on my personal forgejo server to private because llm crawlers were thrashing my server

when you ask chatgpt a silly question to see the silly answer, or prompt midjourney or whatever for a funny image, or use copilot or claude to vibe code, you are complicit in this

@Tak I run gitea/forgejo aswell and I made my own, it works pretty well. The config isn't perfect yet but on the off chance you are using docker I do have a docker compose config example on there.

git.sequentialread.com/forest/

Yeah its very cringe how the LLM scraper bots will try to download both zip and tarball of the repo at every single commit.

@dumpsterqueer I think this is what happened to cyberia's old server when it crashed hard, except it was all / most processes. I never really understood it at the time. I believe ZFS was involved, and it was running out of memory.

@dumpsterqueer

so the kernel is refusing to kill these nodeular processes because they made a syscall (probably io...?) that never returned? Or something? TIL

@feliks I have probably committed "oops" at least 1000 times

Forest boosted

i guess debugging is just turn-by-turn combat with a computer

Show thread

First QueerCoded workshop April 19nth !!! We decided on Saturday afternoon.

@technomancy

I've heard of a lot of different ones of these. Some of them are more black hat than others. But yeah, there's definitely a market for it. It's pretty big.

@notplants This is basically just a list of things that need to be replaced because they have 80s era UIs

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.