X XFediYour place in the Fediverse
XFEDI

Remote profile

ActivityPub
Profile banner

adingbatponder :nixos: 👾

@[email protected]

Tech by the people, for the people.
#iyoga #choir #iyengaryoga
🦀 :nixos: #nixos #reticulum #radicle 👾
(Photo: Steve Carter @GetCarter )
@homelab
LXMF: fa01207bb431ff3aeea472de3e81beab
http://loramesh.i2p/
for sure immediate link to rns git repo use in
~/.reticulum/config:
[[repoducible]]
type = TCPClientInterface
enabled = yes
target_host = repoducible.net
target_port = 57001
name = repoducible
test at CLI:
nc -zv repoducible.net 57001

Open remote profile ↗
Posts

#radicle #heartwood seems to need a release with fix / patch commit 2f930e3561 to be deployed to avoid a CPU on seed running at full pelt for a week for no reason.
https://github.com/radicle-dev/heartwood/commit/2f930e3561194475e76fea63c6a6590fa99f5b1c

GitHubnode/reactor: Terminate transports whose socket is dead · radicle-dev/heartwood@2f930e3A transport whose peer has gone away is never terminated, and the reactor then spins on it at 100% of a core. On every iteration the reactor [re-registers the socket with whatever interests the tra...
↩ Reply ♡ 0 · ↻ 0 ↗ Original

My home-hosted website is being hammered thousands of times an hour by a swarm of coordinated residential IP addresses that do not get used again the next next day but hit with a new batch of addresses the next day. The attack swarm does nothing other than a simple GET & that is it. What can be done? I do not see why one should play along with such coordinated nonsense. Blocking all IP addresses in the swarm would serve no purpose: they hardly any of them are re-used. #suricata #ids #firewall

↩ Reply ♡ 0 · ↻ 0 ↗ Original