cDc/hack.xxx/Veilid
Support Veilid! Badge: ๐ www.veilid.com
Merch at: @hack.xxx
he/him/"hey buddy"
as you descend upon half-time tonight
that we can only approximate half-time to the nearest planck length
and as such, once it is observed it is already in the past
as you descend upon half-time tonight
that we can only approximate half-time to the nearest planck length
and as such, once it is observed it is already in the past
what the fuck but it felt like a zombie movie so i got the fuck out of there.
We got to talk to one of the kids that survived that place, Fred Boyce, before he passed away. Gave us all the stories.
what the fuck but it felt like a zombie movie so i got the fuck out of there.
We got to talk to one of the kids that survived that place, Fred Boyce, before he passed away. Gave us all the stories.
"The OS will prefer modern, more secure Kerberos-based alternatives."
haha NTLM happened in 1993 and Kerberos was a product of the 1986-1993
i guess 'modern, more secure' means 'we fucked up and the other, older, thing was better this whole time'
"The OS will prefer modern, more secure Kerberos-based alternatives."
haha NTLM happened in 1993 and Kerberos was a product of the 1986-1993
i guess 'modern, more secure' means 'we fucked up and the other, older, thing was better this whole time'
3D printed and a thin layer of felt on the bottom and this works really well.
3D printed and a thin layer of felt on the bottom and this works really well.
like where you have to convince a bot that youโre also a bot in order to pass the test, and the bot asks you questions that it thinks will prove youโre not a bot and actually just human?
like where you have to convince a bot that youโre also a bot in order to pass the test, and the bot asks you questions that it thinks will prove youโre not a bot and actually just human?
1. constructors first, because thats the first thing you do
2. public api methods, because thats the next thing you do
3. internal implementation methods if not fully hidden by inheritance.
4. fields because nobody gets their scope right anyway
1. constructors first, because thats the first thing you do
2. public api methods, because thats the next thing you do
3. internal implementation methods if not fully hidden by inheritance.
4. fields because nobody gets their scope right anyway
because you are faced with a decision with no right answer
just remember that in some github issue
github.com/dart-lang/sd...
people are trying to decide if constructors or fields come first
and no matter what they pick
everyone is gonna hate it
because you are faced with a decision with no right answer
just remember that in some github issue
github.com/dart-lang/sd...
people are trying to decide if constructors or fields come first
and no matter what they pick
everyone is gonna hate it