

There is absolutely nothing wrong with tor/i2p having their own fediverse. Just it becomes as fresh as dreaddit (pretty sure I spelt that wrong).


There is absolutely nothing wrong with tor/i2p having their own fediverse. Just it becomes as fresh as dreaddit (pretty sure I spelt that wrong).


Yes, the problem is how does a clearnet instance send you content to your equivalent of an onion address?
None of those speak to the reliability of iptables. They all sound like skill issues.
In 15 years of network engineering iptables has been the simplest part.
A layered approach with hardware firewalls is valid but when those firewalls get popped, looking at you Cisco, Fortinet, and PA you still want host level restrictions.
Your firewall or switch should never be used as a jump host to servers
iptables and firewalld are not reliable
Can you give examples of that?


Seeing as most root CA are stored offline compromising a server turned off is not really possible.
I’m more annoyed that I have 10 year old gear that doesn’t have automation for this.


I recall a story years ago that whenever Ann Hathaway has a bad news story Berkshire Hathaway also takes a dip because high frequency trading scrips are idiots.


I like to go by the Veeam variant. 3-2-1-1-0
3 locations
2 sites
1 offsite
1 write permission (write Once read many backup)
0 days since last success.


May as well crack out DC++ and start heading your files.


All good mate.


I must be thinking of the wrong Wireshark because the one I know of is a packet capture program not a VPN client/server.
Silly phone.


AI scrapers are the new internet DDoS.
Might want to throw something Infront of your blog to ward them off like Anubis or a Tarpit.


But they don’t run CLNS so the ISO model doesn’t fit either.


How don’t they fit?


IP is the internet layer which is layer 2 and TCP is the transport layer which is layer 3.
Why split physical and data link when they are so closely related? You can’t use vpi/vci on an ethernet port, you can’t use MAC addresses on a frame relay port. Bundle that shit together.
Presentation, application, and session are all dealt with by the application anyway so why bother splitting them out from a network point of view?


Easier way is to remember that the ISO model is defunked and you should use the TCP/IP model.


When I saw who was purchasing them I knew it was bad for the hobbyist users.
QC is such a bad company. Sueing their customers because they want to use non QC chips in phones with QC chips.


Consider if you need three/five nines uptime. I know I don’t so I don’t worry if jellyfin or tickdone are down for a few hours.
Using the Agile framework we built our fault tolerant app to maintain uptime even when the individual micro service fails to maintain our 9.999 SLA.
/S