/Cinny 
Posts
22060Following
432Followers
827lotte adds rac- to words a lot but it doesn’t alter meaning
NSFW posts are not for minors (they will be blocked on sight).
Opinions expressed in this profile are representative of those of your employer.
“u are my favorite therianizing biohazard” — @sodiboo@gaysex.cloud
“you know, maybe i will finally learn to read the content warning before clicking 'view' [—] thanks for this lesson @charlotte” — @ariadne@social.treehouse.systems
pfp by @5225225@furry.engineer
/Cinny
repeated
Eloy
eloy@hsnl.socialGeorge Orwell forgot to account for that the surveillance industry runs on outdated Android builds and fragile aluminium pipes
0
3
1
/Cinny
repeated
/Cinny
repeated
/Cinny
repeated
⛧-440729 [sophie raven]
sophie@catgirl.clouddas internet, wenn es von siemens erfunden worden wäre: transportschichtsicherung-servierernamensidentifikations erweiterung
0
2
0
Charlotte /Cinny
charlotte
1
2
5
/Cinny
repeated
KDE
kde@floss.socialKDE's goodies 🧸 shop opens its doors!
https://tube.kockatoo.org/w/wNSDG2dYZFALMoX79dVpU4
Check out what will soon be your one-stop location for all KDE-themed merch.
Our first item, the adorable Konqi soft toy is already available for pre-ordering (if you solved the riddle, congrats! You already know this, but for everybody else...):
https://merch.kde.org/products/konqi-plushie
#merch #toys #plushies #konqi #FreeSoftware
3
8
0
Charlotte /Cinny
charlotte
@endrift @nasser @0xabad1dea before i turned off the bridgy bridge for my account every single time i complained about “bluesky is centralized” issues folks that are working on ATmosphere projects are suddenly very interested in proving me wrong
0
0
1
/Cinny
repeated
/Cinny
repeated
kimapr ☭ 🇺🇿 ⚧ ⚢ ❤️🧡🤍🩷💜
kimapr@ublog.kimapr.netCoyote vs ACME (he is trying to obtain a TLS certificate)
0
6
3
/Cinny
repeated
/Cinny
repeated
[4FBB09]
5225225@furry.engineer@charlotte @tully @SharpLimefox @eri @illyBytes one thing i've been looking at is something like https://git.2f30.org/stagit/file/README.html as a post-push hook on the server
"take this git repo that exists locally and pregenerate html files for stuff like "view specific commits" (O(n) and easily generatable once) / "view the log" etc
you wouldn't get "generate a diff from foo..bar" but that's fine. you can either say "just fuckin clone it yourself" (or, the more silly option, have a in-browser JS git client which clones it and then runs ops locally... that wouldn't scale for every op on a large repo though)
and then it's a bundle of static HTML files which is servable at the rate of your bandwidth (and reasonably easy to cache)
0
1
1
Charlotte /Cinny
charlotte
@SharpLimefox @tully @eri @illyBytes software performance and what WAF you use are like the two main knobs you can turn here, and basically i think that WAF is at most a bandaid that mainly introduces more issues than it really solves (the underlying issue is usually the software having problems)
and a lot of the anti-scraper WAFs also misunderstand both the problem and the solution extremely hard (like iocaine for example which instead of closing the connection just slowly feeds it markov chain generated data)
1
0
1
Charlotte /Cinny
charlotte
@eri @SharpLimefox @illyBytes @tully (basically i also don’t think that it’s possible to make git forges fast while continuing to use git on the backend, git is primarily built for the local workspace usage and not for that of any git browsing tool. Like the worst case scenario for reading a file from storage is that you need to read every commit that changed the file)
1
0
1
Charlotte /Cinny
charlotte
@eri @SharpLimefox @illyBytes @tully nextcloud should be fine, despite being ungodly slow usually since the only thing it can access is the login page (and maybe a few related pages) and some assets
gotosocial is probably less of a problem than forgejo, seems decently fast to me at least
1
0
1
Charlotte /Cinny
charlotte
1
0
2
Charlotte /Cinny
charlotte
@eri @SharpLimefox @tully @illyBytes yeah forgejo has a lethal combination of “unoptimized backend” (fucking git) and “an extremely large amount of link targets” which makes these scrapers make a lot of requests in a way that is overwhelming
for git in particular looking at files themselves is also expensive but at least there tends to be fewer of those than number of commits * number of files
2
0
2