Searching We.Love.Privacy.Club

Twts matching #blackhole
Sort by: Newest, Oldest, Most Relevant

Tenstorrent Blackhole Support & Other New RISC-V + ARM64 Hardware In Linux 6.19
The set of six branches containing SoC and platform updates/additions for the Linux 6.19 kernel have been merged for enabling a lot of new RISC-V and ARM 64-bit hardware as well as enhancing some existing SoCs/platforms… ⌘ Read more

⤋ Read More

So blackholing my Gitea instance’s DNS for the day seemed to have worked 🤣 (if only I had a real target I could have made their fucking crawlers DDoS themselves šŸ˜‚) – Let’s also see if enabling DDoS proection on the Edge via Vultr’s DDoS capability also helps? šŸ¤”

⤋ Read More
In-reply-to » @movq Today I had unexpected old twts after jenny -f. Have now jennys cache under revision control, automatically commiting changes after each fetch. Let's see if this helps finding a (possible) bug.

@movq@www.uninformativ.de Your scenario would produce observed behaviour, agreed. On the other side I’m sure I’ve set very URL in lasttwt > 1630000000.0 (manually, in my editor).

But I can’t reproduce any weird behaviour right now. I’ve tried to ā€œblackholeā€ twt.nfld.uk temporarily. That does not have any effect.

I’ve also tried to force twt.nfld.uk to deliver an empty twtxt. That does not have any effect either.

So I guess everything is fine with jenny.

I have wrapped jenny into some shell script to versionize ~/.cache/jenney. This way I have better data if anything unexprected is showing again.

⤋ Read More