æʃliŋ, medical grab-bag @aescling@cat.family

@The_T @wallhackio @vaporeon_ that’s a pretty good one

@The_T @wallhackio @vaporeon_ oh no yeah i’ve definitely furgotten a lot of evolutionary stages’ names. skill issue

@The_T @wallhackio @vaporeon_ he chooses the wrong games

@The_T @wallhackio @vaporeon_ part of me wants to say i could name them all (if given images, i definitely couldn’t recite the national dex on command) but the wiser me knows i’d purrobably furget something’s name

@wallhackio @vaporeon_ @The_T

@vaporeon_ @The_T @wallhackio it’s a starter, i think he could have guessed

(also don’t use GitHub)

@vaporeon_ @wallhackio granted, a lot of those lines of code are dependencies of development tools (eslint, the TypeScript compiler, webpack, etc. etc.); most purrojects aren’t purrobably really linking with anywhere near all of those 200MB’s worth of javascript

it’s still ludicrous though

@vaporeon_ TLS 1.3 might never land in BearSSL because it apparently literally cannot be implemented without malloc, which contradicts with (one of) BearSSL’s design criteria

@vaporeon_ @wallhackio combined, sounds plausible fur many purrojects

my anti-bot bot is buggy it seems

@vaporeon_ i would recommend getting 1.3 to work if you can but i think it’ll be fine if you don’t

@vaporeon_ https://ssl-config.mozilla.org/ offurs a (non-default) “modern” recommendation fur TLS 1.3 only configurations, which is suggestive that people will eventually try to make 1.3 the floor of suppurrted purrotocols. overwhelmingly though you should be able to get away with TLS 1.2 suppurrt in your client in the near future and reasonably moderate future

@vaporeon_ apt --update $command is more or less equivalent to apt update; apt $command. so now apt --update upgrade is a convenient little one-liner fur the common act of checking fur package updates

it made it into the current Ubuntu LTS as well