Penistone and Scunthorpe

PROTON_FSR4_RDNA3_UPGRADE

oh nice addition, had to tweak this manually on CP2077

did you apt update beforehand ? it is weird that it’s trying to install lower level libc6

before getting a pocketbook I was using ReadEra and it worked alright (for basic reading)

thinking about this, wouldn’t the best way to hide a modern websie be something along getting a wildcard domain cert (can be done with LE with DNS challenge), cnaming the wildcard to the root domain and then hosting the website on a random subdomain string ? am I missing something

crt.sh and certificate transparency

weren’t chucklefish the ones that strangled this game in the first place?
now take this with a big chunk of salt, I do not remember at all if this is any true but feel like I read it somewhere

sandustry ˢᵒᵒⁿ

have not hear anything bad about webp, whats up with that

fyi you have toggled the setting that marks you as a bot account, as such your content will not show for some percent of people that have bots hidden

https://store.steampowered.com/app/3211720/Erosion/

don’t know the details but my general IT knowledge says that: single unicode character/glyph can take up to 4 bytes instead of 1 (ascii).

I mean I might have a laughing pikachu tattooed, from my side you are good

have been eyeing elixir for a while, should give it another try. the whole beam/otp/erlang is a bit scary though

hopefully it’s good, don’t want to mix work and personal stuff

Little bits and pieces but mostly bug fixes - I like my shit working but maintenance is not my strong suit, more of a traveling contributor or drive-thru fixer.
I believe I fixed calling in one electron messenger.com wrapper before - that was fun but these days I usually try to help the game BAR whenever I have extra time.

Edit: Keep forgetting but I am also maintaining few apps on AUR, nothing big except for maybe one helper tool/calculator for EVE online

bookmark folders

unsure if the translations work well in english but checkout Christian Morgenstern, he made similar “silly” poems

Linux has kind of two forms of memory pages (entries in RAM), one is a file cache (page cache) and the other is “memory allocated by programs for work” (anonymous pages).

When you look at memory consumed by a process you are looking at RSS, page/file cache is part of kernel and for example in btop corresponds to Cached.

Page cache can never be moved into swap - that would be the same as duplicating the file from one place on a disk to another place on a (possibly different) disk.
If more memory is needed, page cache is evicted (written back into the respective file, if changed). Only anonymous pages (not backed by anything permanent) can be moved into swap.

So what does “PostgreSQL heavily relies on the OSs disk cache” mean? The more free memory there is, the more files can be kept cached in RAM and the faster postgres can then retrieve these files.

When you add zram, you dedicate part of actual RAM to a compressed swap device which, as I said above, will never contain page cache.
In theory this still increases the total available memory but in reality that is only true if you configure the kernel to aggressively “swap” anonymous pages into the zram backed swap.

Notes: I tried to simplify this a bit so it might not be exact, also if you look at a process, the memory consumed by it is called RSS and it contains multiple different things not just memory directly allocated by the code of the program.

Had to solve the same problem few months ago, user provided content and so, user provided translations.
We use postgres everywhere and we had to support 3 languages initially with one more eventually, so we decied to use json fields for anything that could be translated (which wasn’t too much). Mind you, this was basically a (temporarily permanent) prototype project but (fresh) postgres has a good support and operators for json so it worked alright.

EDIT: I remembered that hstore might be a good alternative too, I think it was slightly less “heavy” and had better operators for the kind of access we needed