DoeNietZoMoeilijk 🥔 @doenietzomoeilijk@mastodon.nl

@berkes Oh wow, that's... precious.

@FreePietje to be brutally honest: you talk about the outdated distinction between left and right, and then adding to that same distinction. 😉

@soc *CLICK*

@sp1rit @sneak ah, never thought about mobile Chrome not having extensions - it's been a while since I used it, and when I do it's only to test stuff.

@sneak @sp1rit https://chrome.google.com/webstore/detail/redirect-amp-to-html/kifkmmpiicbcnkjaliilaoeaojlldonl that might at least work for Chrome, I suppose.

@kline a \0 on your nick? Oh my, now your remark about breaking clients the other day makes sense. 🤣

@sean basically, this, yes.

Crawl through the code, inspect objects and their methods, grab the doc blocks or what have you to complete the picture.

The better ones can tell you where each method was used, too, which lets you jump around quickly and refactor easily (change a method name and the IDE ensures all calls to that method get updated, too).

There's a bit of a standard around it, nowadays: https://microsoft.github.io/language-server-protocol/

@amolith that post is from 2013, and things haven't gotten any better, really. The more pervasive and ubiquitous and *normal* computers have become, the less people know how they actually work.

@martijnbraam but will it blend?

RT https://nitter.net/JayTaph/status/1352620044409307138

We just released our "hello world" version for BitMaelum: our new encrypted e2e mail system: bitmaelum.com/ https://github.com/bitmaelum/bitmaelum-suite #crypto #e2e #privacy #mail #golang

@gunkslinger This speaks to me.

@berkes if it doesn't arrive, it can still be valid. Your e-mail could end up being junked, or the receiving mail server doesn't implement the protocol properly, or it's just having a really bad day, you know.

Of course, it it does end up in a mail box, you can be reasonably sure that the address is valid. But only reasonably. Not fully. Never fully.