Replying to
@snailerotica the options are too binary. I think I queered the human/nonhuman binary too hard
(understandable if there's no more options allowed for polls)
Remote
jackson& 
, the clock of all time
@jacksonchen666@micro.jacksonchen666.com
mastodon 4.4.0-alpha.5+chuckya.jacksonchen666live streaming my AuDHD :ms_neurodiversity: brain to the internet (wordplay, grumbling, jokes, nonsense), pretty much all about computers (mainly sysadmin of jacksonchen666.com) with markdown formatting
overexperienced computer toucher, amateur photographer (@photo@gts.jacksonchen666.com), and interested in a normal amount of too many things to remember. also a professional nonsenser
a form of an agendered (TODO: find lost gender) demi-nonbinary aroace(?) 
they/it or any/all creature (ΘΔ?). computer masochist who will put up with the weirdest issues. vaguely plural shaped with sometimes difficult to discern headmates
disclosure: white[clarify], abled, [REDACTED] years old, [etc.].
extremely not fond of those age gating their profiles for any reason related to legal reasons.
follow request acceptance generally requires me to follow back (which requires similar interests). follow requests are vetted whenever, but may be bypassed if we already know each other somewhat. repeat follow requesters are notified then blocked.
fedi DMs are pretty much open, in fact required to be able to contact me on matrix (separate spam from legit contacts)
current mutual aid status: I currently don't exactly have money I can freely send, best I can do is a boost unfortunately.
(i do have pluraldawn (https://exa.y2k.diy/garden/pluraldawn/) installed, but this only applies to my web fedi client. i don't use it for myself though)
0 Followers
146 Following
14 Posts
Joined November 25, 2021
pronouns:
they/it. or just assign anything, not like I can decide ¯\_(ツ)_/¯
gender:
slightly nonbinary :ms_deminonbinary_flag: agender :ms_agender_flag:
languages:
en-US (unsuitable for general use: hu, zh-CN)
中文 (zh-CN):
我只能听和说中文，我不会写和读中文
magyar (hu):
Az ényem magyar nem nagyon jó (szókincs rosz)
my wiki:
site (& blog):
backup account:
page of pronouns:
matrix:
ask (required due to interactive processes)
stoat chat (unchecked):
jacksonchen666#4595
other contact methods (delta chat, email):
$€¥ (pending):
offshore alt/private/headmate:
(plural) members:
2 links above + any undiscovered ones (still in the process :P)
currently preferred respirator:
uhhh
Future™ account (follow this too):
keyoxide:
$argon2id$v=19$m=512,t=256,p=1$DDvlV3iDTUW7c/I8YHtjVA$zw7GcDs3mZARqIY/dffHAba5EUfJrSX+LFFLDRWmQcM
Replying to
@Kuniti_shino@pounced-on.me
mkdir build
cd build
cmake ..
make -j16
if dependencies aren't there then cmake will error I think. get dependency and try the cmake command again
Replying to
@navi suitable for a work environment? i have no idea, i am not a good judge for that :p
Replying to
@aphyr@woof.group blocking unauthenticated access to some APIs might not do much, especially if the scrapers are not hitting API endpoints.
anyways, you might be interested in iocaine plus nam-shub of enki (iocaine author's personal request handler, which covers a lot already), and it gives garbage when it suspects scraper (and also brave and ladybird browsers, because fascist made browsers). here's a setup tutorial. note that for the nginx stuff, i recommend you apply the map stuff related to request methods documented in https://iocaine.madhouse-project.org/documentation/3/reverse-proxies/nginx/#integrating-iocaine or otherwise you will run into issues with uploads (https://git.madhouse-project.org/iocaine/iocaine/issues/109)
the only major caveat with iocaine in general is that false positives might be much harder to deal with, you basically have to edit the code for nam-shub of enki or your request handler. there is user agent allowlisting which should work as a quick temporary fix, i think.
(i cannot recommend anubis, the author behind it is unironically using "AI" and also has a history of doing so. i don't know why they're still maintaining anubis)
Replying to
@Seirdy@pleroma.envs.net *pats on head*
Replying to
@mynameistillian@plush.city biblically accurate discord tho
Replying to
@mynameistillian@plush.city yeah upon a second look the preview image is probably slop 🙃 the slack logo is wrongly shaped and colored and discord... well yeah lmao
Replying to
@mgorny@social.treehouse.systems what I've appreciated in gentoo is that I can just say no to specific versions of packages. new bug that doesn't happen in older versions (and will be fixed later)? I can just mask it, downgrade it, and then I don't have to be bothered by it anymore (most recently: the watch command broke terminals that resized, requiring a full program restart)
oh and patching! mostly to get fixes for annoying bugs ahead of time (e.g. mpv eating CPU resources when the clipboard contained something, fixed in 0.41.0) but sometimes also to bend software my way (glfw so that minecraft works as expected on wayland, including but especially mouse cursor positioning)
oh and multiple versions of packages! even for SLOT=0 packages because of downgrading, but also not having to fallback onto external [language] version managers
and portage/emerge/the package manager in gentoo reminds to do other things, like cleaning up packages after upgrades. that's neater than having to remember all the steps required for doing regular system upgrades including cleanup. oh and what to do when the backtrack limit is hit too
gentoo also felt like the distribution where making my own packages/ebuilds has been quite low friction to start. it's not been successful for me with fedora COPR at least twice so far, and with gentoo i've been getting the hang of it fairly well so far
gentoo has been pretty neat even though i dived right into it with like, not really much of an expectation of anything specific. i wasn't even initially using gentoo just because i can compile things with Performance Flags™, but now i have all of that to say "gentoo is kinda neat"
Replying to
@tenacity maybe more dead than matrix :D
Replying to
@1 pkg!
Replying to
@kescher dang
Replying to
@2something @Ember well that settles things real hard
Replying to
@Ember has there been any attempt to convince maintainers otherwise which has failed? I've not yet
Replying to
@olivia@pl.firechicken.net horrendous :DDDDDDDD
i'm still stumbling over whether it was 1.117.0 or 1.118.0. the complaints only really seem to have started around 1.118.0, but github says the commits are part of 1.117.0. i guess it was part of 1.117.0 then
well time to hack in extra special checks for this special case :p