It’s just 42.zip
I’m boring and I shitpost and tech-post all over the place. Big fan of Ea-nāṣir.
Microblogs: @shittykopper@toots.w.on-t.work
It’s just 42.zip
(Funnily enough, the Cisco in-house messaging and video calling solution we use at my work, through which we also receive landline calls, is still running on XMPP to this day, so I sorta became a XMPP user after all…except I haven’t started this software in 10 months because fuck landline calls and we have better alternatives for chatting.)
XMPP is still chugging along on the backends of stuff like that. I’m not sure but I think WhatsApp has some XMPP in it still.
The most ironic one though is Jitsi, which is what Matrix uses/used (until they started working on Element Calls) to do video calls.
I believe, with Authorized Fetch (what Mastodon calls secure mode) blocking intermediaries won’t be needed, as instances will have to cryptographically “authorize” themselves to receive/send data, and you can just say “no” to any requests coming from threads.net, acting basically as a “defederation enforcement mode”.
I could be wrong though, haven’t caught up on the exact details.
Thoughts, prayers, and getting the low hanging fruit down (disabling root login, ssh public keys, updates)
As long as .world doesn’t defederate them back, Beehaw can re-federate whenever they want.
That’s the eventual goal.
Or, well, something like it.
Community names are, by default, limited to 20 characters only. No errors or anything pop up when you exceed that, but you can ask your admins to extend the name limit.
I used to mess around with CSS and even made some reasonably popular themes (not under this username ofc) so I had like 4 private subs.
& it turns out it’s already in your inventory
respect to our hard workers, tirelessly working the content mines, all for nothing but a handful of up votes
.social + .online are the mastodon equivalents of lemmy.ml, except they’ve been through several mass migrations already so they kinda know what they’re doing
.world is (perhaps un)surprisingly the mastodon equivalent of lemmy.world, same admin and all
but tbf https://joinmastodon.org is so much more polished than join-lemmy that it’s actually worth going through instead of just piling on the largest
To be fair, PHP has slowly been getting it’s shit together since PHP 7, and 8 seems to be in a reasonably great shape compared to the horrors of 5.6
get rotated idiot
(lemmy removed the rotation data from the image alongside shit like location info. i think there’s a github issue to not do that but no idea when the devs will get to it)
Microservices aren’t a silver bullet. There’s likely quite a lot that can be done until we need to split some parts out, and once that happens I expect that federation would be the thing to split out as that’s one of the more “active” parts of the app compared to logins and whatnot.
So when are we readying the Matrix homeservers?
…and getting Element to care about chat UX rather than throwing Matrix at any other problem they can think of (no we do not need a vr metaverse but FOSS)
aside from moderation stuff, smaller instances tend to be faster and, ironically, more reliable in the shorter term, as they’re not constantly getting hugged to death
and in the long term while they may be more vulnerable to running out of cash and shutting down, they’re less costly to maintain overall, so as long as people chip in that’s not as big of a concern
Surprised you haven’t listed !196@lemmy.blahaj.zone on memes. It’s surprisingly active (if you’re not used to it from Reddit already)
Well you’re in luck because Lemmy 0.18 rips out all WebSocket code.
Not OP but I can answer with my own stats:
In just a week, With BTRFS compression (compress-force=zstd:3) & deduplication (via bees), media is at about 1GB (and I am subscribed to media-heavy communities like 196) and the postgres DB is at about 550MB (which is also currently shared with Matrix Dendrite)
At “idle” (as you can be while being connected to ActivityPub & Matrix), the immediate CPU and RAM usage breakdown per container is:
NAME CPU % MEM USAGE / LIMIT MEM % NET IO BLOCK IO PIDS CPU TIME AVG CPU %
pict-rs 0.20% 18.92MB / 4.005GB 0.47% 3.319GB / 1.105GB 17.58GB / 3.239GB 13 1h16m57.232828s 0.59%
crowdsec 1.39% 44.23MB / 4.005GB 1.10% 106.4MB / 23.46MB 25.53GB / 486.7MB 11 45m28.744419s 1.95%
caddy 0.63% 73.06MB / 4.005GB 1.82% 1.675GB / 1.977GB 3.322GB / 720MB 10 21m9.94572s 0.90%
dendrite 1.58% 197.7MB / 4.005GB 4.94% 912.8MB / 2.33GB 8.718GB / 4.761GB 12 53m26.302022s 1.43%
postgres 5.33% 82.51MB / 4.005GB 2.06% 56.22GB / 7.961GB 20.92GB / 295.7GB 23 8h20m28.078567s 2.86%
lemmy-ui 0.00% 48.71MB / 4.005GB 1.22% 3.491GB / 5.961GB 3.603GB / 5.267GB 12 31m35.884936s 0.24%
lemmy-be 2.82% 29.01MB / 4.005GB 0.72% 16.45GB / 57.85GB 7.966GB / 6.439GB 6 3h6m34.633508s 1.42%
Net IO you shouldn’t really care about as that includes inter-container networking. I’m trying to find how much outgoing data have been transferred but because the month just ended I have no idea how accurate the numbers are.
Reminder: ButtFish is a thing