@feld
Up and not crying
Relays (1)
- wss://relay.ditto.pub – read & write
Recent Notes
@Blurry Moon @menherahair :redeyeorb: @Phantasm @ we should make a social network for men who are unemployed or on disability, it will have all their favorite people on it
@ @menherahair :redeyeorb: @Phantasm why should a reply my friend made to someone I don't even know be blasted to my timeline, it's like this image just sending your boys in for backup
@GNU/翠星石 this is simply the easiest way to demonstrate the bug... and proprietary software? wtf are you on about?
@nprofile1q... @nprofile1q... oh shit you made the mistake of posting publicly again, I hate when that happens :doh: it's a shame that people can see what you write if you press the Post button, it even gives the option to respond isn't that weird?
@nprofile1q... @nprofile1q... whoa how did you come to the conclusion that I care about any of this and that I don't instead love making fun of people who are outraged by Mamadani's existence
@nprofile1q... @nprofile1q... I can't believe Mamdani redirected the funding for the Pfizer building columns and gave it away to the welfare queens. This could have been prevented if we voted harder.
"outdoor" cats have done enough damage to our environment/ecosystems, it's time for the USA to pass laws allowing trapping/shooting of them as varmints tbqh
1
> seriously, OpenSSL 3.0+ is really REALLY badly performing compared to 1.x
do you have AI bots pounding your servers? Your server is falling over faster thjan it should because of OpenSSL. It could probably handle more traffic if you switched to WolfSSL or AWS-LC
https://www.haproxy.com/blog/state-of-ssl-stacks
> OpenSSL 3.1 tried to partially address the [locking abuse] problem by placing a few atomic operations instead of locks where it appeared possible. The problem remains that the architecture was probably designed to be way more dynamic than necessary, making it unfit for performance-critical workloads, and this was clearly visible in the performance reports of the issues above.
> After everything imaginable was done, the performance of OpenSSL 3.x remains highly inferior to that of OpenSSL 1.1.1. The ratio is hard to predict, as it depends heavily on the workload, but losses from 10% to 99% were reported.
STOP 👏 USING 👏 OPENSSL 👏 FOR 👏 TLS 👏
do you have AI bots pounding your servers? Your server is falling over faster thjan it should because of OpenSSL. It could probably handle more traffic if you switched to WolfSSL or AWS-LC
https://www.haproxy.com/blog/state-of-ssl-stacks
> OpenSSL 3.1 tried to partially address the [locking abuse] problem by placing a few atomic operations instead of locks where it appeared possible. The problem remains that the architecture was probably designed to be way more dynamic than necessary, making it unfit for performance-critical workloads, and this was clearly visible in the performance reports of the issues above.
> After everything imaginable was done, the performance of OpenSSL 3.x remains highly inferior to that of OpenSSL 1.1.1. The ratio is hard to predict, as it depends heavily on the workload, but losses from 10% to 99% were reported.
STOP 👏 USING 👏 OPENSSL 👏 FOR 👏 TLS 👏
I've seen more things built on Delta Chat in the past 6 months than anything has been built on Veilid in the past few years :laugh:
and Delta Chat isn't even an overlay network, but you can certainly build entire applications on top of it like it is!
honestly Iroh is always going to be a better solution than Veilid anyway
and Delta Chat isn't even an overlay network, but you can certainly build entire applications on top of it like it is!
honestly Iroh is always going to be a better solution than Veilid anyway
> OpenWrt One – Open Hardware Router
*click*
No SFP+
*close tab*
*click*
No SFP+
*close tab*
1
