kinda sad that the most realistic way is to wear a kigurumi and hadatai 24/7 but even then its pretty much impractical
fuck i want a proper full dive vr
even deno's std kinda sucks. i really don't like some of their design decisions and the direction they're going with it, embracing the web standards and all. bruh..
@[email protected] put on mute by default so it doesn't bother as much 🤷♀️
and like. at least it was not some guy sending you unsolicited uhm.. lewd pictures
(some time ago that happened for me every few days :haggard:)
fuck i really wish we had zero cost abstractions in typescript.
im having a very hard time rn choosing between performance and abstractions and finding a middleground that would satisfy me... kalakdksljdkdaldjks
holy shit people actually care about eurovision
i always thought it was like. that thing for the elderly who don't know how to use streamings, for whom it's the only time of the year they can listen to semi-decent music
@[email protected] @[email protected] btw there are already some custom mtproto server implementations
the most complete are probably [teamgram](https://github.com/teamgram/teamgram-server) and [mytelegram](https://github.com/loyldg/mytelegram) (though they're both only half-opensource, they are targetting businesses), and others are mostly just toy servers to test custom clients and pretty much abandoned, but still worth mentioning – [piltover](https://github.com/DavideGalilei/piltover), [gotd's one](https://github.com/gotd/teled), [Ferrite](https://github.com/aykutalparslan/Ferrite)
@[email protected] @[email protected] mtproto fucking sucks. i too am making a library for it, though not nearly as popular as lonami's. too many edge cases and retrofitting and reusing shit a ton, probably because of tight deadlines put on the devs by durov.
the fact that mtproto sucks is universally agreed upon, probably even by the official client devs themselves. [here](https://habr.com/ru/articles/472970/)'s a nice article about that, if you're interested enough (in russian though)
the fact that they have an official implementation (tdlib) that's not used in any of the official clients alone is hilarious. client devs just don't have the time to port them to it. tdesktop dev tried once (just for fun, out of his own will), and it ended up being half-abandoned soon after because durov just keeps pushing stuff and he doesn't have the time to deal with the tech debt. and looking at clients/ton node code (it's awful), i'm pretty certain that the backend code is pretty much just as bad
@[email protected] tbf crypto exists
but otherwise – largely agree. another big reason is that people from sanctioned countries still exist and are still people..
@[email protected] @[email protected] does it? it's like the first time i hear about that. i know they made some ssr improvements in react 19, but it still is intentionally library stuff...
ok it probably is not a misskey moment, switching a proxy for another one reduced the 503-s to zero... but now i get `Client network socket disconnected before secure TLS connection was established` at a similar rate...
fuck i hate debugging network issues, why do they keep following me everywhere
@[email protected] the entire dom is basically an event system. the entire javascript language is one big event loop :D
in a nutshell: in react functions are called every time the component is "rendered". and the returned jsx is then diffed (aka vdom diffing) and the difference is then applied to the actual dom.
and hooks allow you to "hook" into that process and persist data between renders or do something on (un)mount or when data changes.
@[email protected] https://react.dev/reference/react/hooks
the main ones you'll need are `useState`, `useEffect`, maybe a bit of `useRef` and `useMemo`/`useCallback`.
@[email protected] maybe something along
```dockerfile
FROM golang:1.22.2-alpine3.19 as go-bin
FROM caddy:builder
COPY --from=go-bin /usr/local/go/bin/go /usr/local/go/bin/go
```
would work?
though idk how much go compiler itself is self-contained
> error: Failed resolving types. Importing JSR packages via HTTPS specifiers for type checking is not supported for performance reasons. If you would like types, import via a jsr: specifier instead or else use a non-statically analyzable dynamic import.
fucking what now. why. how is fetching from a url any different from fetching from a url via `jsr:` :haggard: