Nelind

the l was literally the main thing that made my ditch the idea of ever trying maple mono :3

i dont want l to be the single cursive letter in my otherwise monospace block character font thats just ... what

i feel like thats likely to not happen though ... mainly cause of stuff like screensharing portal and co. stuff that needs tight integration between compositor and some part of the DE

at least plasma with proper tiling .... please ... i beg you ... all the scripts are shite ... just implement tiling in kwin. being not QT mostly because QT theming is a mess. so like fork is fine too

i really hope that plasma regains the ability to run on not kwin cause mmm plasma on comsic comp

okay finally sat down and tried cosmic (one line config edit thanks nixos <3) and aaaaah its frustrating. not because its bad because its soooooo close to being exactly what i want!! and then *just* misses :<

i think at this point my ideal desktop is plasma built on iced and with tiling or smth

ne hes right thats an abomination

alternatively ig it could send over HTTP/3 back to the origin server but rev proxies are often used as TLS termination to avoid origin servers needing to deal with TLS, certs, etc. so idk if thats a viable option either

a reverse proxy has to be able to inspect the contents of a request to make proxy decisions so basically with HTTP/3 ig we need to configure our rev proxies to accept HTTP/3 and then proxy down to the protocol level for HTTP/2 internally on to the origin server. that feels messy but ig it works ...

idk how i just learnt that QUIC enforces the use of TLS style decryption. idk how to feel about that ... on the surface thats good ig? encryption is good the main issue i see is for things like reverse proxies. a major tenant of todays infrastructure design is reverse proxies

Rt if you love titties

voice kink voice kink voice kink voice kink voice kink voice kink voice kink voice kink voice kink voice kink voice kink voice kink voice kink voice kink voice kink voice kink

i keep rewriting my rewrite of myccorizhals client error modeling cause i dont like how its turning out but i think i need to start accepting that i wont *really* like how its turning out until XRPC itself gets better error modeling and servers conform to it. gonna make it the best i can though

to a certain extent this is also a result of the atproto specs being so .... unspecific. theyre not really written like specs. and in some ways thats nice. theyre a lot easier to read than proper specs. but it also means that many parts of the system are under specified

i like to joke around sometimes at how PBC seems to sometimes fail at implementing their own design according to their own spec but im starting to realise my joking may be closer to the truth than at all comfortable .... or at least especially when it comes to XRPC

the reference impl never and i mean *never* responds with that. the relevant type is literally never contructed: github.com/search?q=rep.... instead when it ought to return that it will instead return a 400 with InvalidRequest and a message saying resolution failed matching neither lexicon nor spec!

the more i work on myccorizhal the more i find weird shit like this that are weird and annoying. the lexicon for com.atproto.identity.resolveHandle specifies a HandleNotFound error that will supposedly be returned if resolution determines the provided handle doesnt point to any account however

My kinks could kill a Victorian man

pub struct Nel(Autism);

impl Nel {
pub async fn yap() { /* ... */ }
}

i have neither and thats literally only cause i cant be arsed + one of my friends let me leech of of their dropout sub (i should get my own at some point). dont think they have a nebula sub either tbh

yk i never thought about it before but dropout and nebula could absolutely do partnership. like the viewer base overlap is big enough that that would absolutely work

control panel, not that control panel, no not settings either, i mean the control panel from the windows version released in 100 BC. no sorry they actually moved it you now need to ask copilot to change that for you with your voice, oh nvm they changed it again its now only available in the eu

yes hun yes it is 🫂 i did that literally earlier today

:<

how are double negatives pet brained!! :<

:3

i will never not want to be a deskpet

my best guess as to how you heard this is that it mightve be a game of telephone out from the fact that the shape of bookmark data is defined in lexicon (despite not being a record) so as to hopefully make a future migration to private data easier?

either way the preferences api is not generic or usable/useful enough to support something like drafts. its purely a stop gap and not even that great at being that tbh (to the point where there has been one or two bugs of the client fully clobbering all preferences when wanting to update one).

so it mightve moved over there already im honestly not sure. in general preferences are a mess and theres a contention on what to do (until we have a proper private data solution) between: store it on appview and follow spec or store it on PDS as an out of spec special casing.

labeller subscriptions, label setting and other preferences are set in the preferences api yea. which has special casing on the PDS to be private. though i think theres been some talks about moving it to the appview? im not exactly sure. iirc the proxy header *is* added to pref requests these days

but idk if asterism comes a bit too close to microcsm and constellation to maybe confuse folks

okay i keep going back and forth on name ideas for the overlay appview thing. hyphae makes sense and follows my general "plants or fungi related" theme for my project names but also i really like hyphae and idk if i wanna use it here. also considered asterism as in "part of an appview constellation"