paulsnar @paulsnar@mastodon.technology
My spec reading spree continues, and the Scuttlebutt protocol guide is still really nice to read: https://ssbc.github.io/scuttlebutt-protocol-guide/
It's a bit unfortunate that it requires deviating from the regular JSON convention that keys within objects may be unordered (and hence goes against the general ideas of them being just hash tables) but I suppose that's the historical baggage that any project has some of.
Byte is here. https://byte.co/
Suggest following Tragic_Tofu, they were great back in the day.
I suppose for many it must have made intuitive sense, I'm just pointing this out for myself.
Now that I think about it, compression algorithms seem to be a fair measure of entropy—if your data compresses poorly, it must be pretty random.
Of course this isn't an absolute measure, but it feels like a fair heuristic to an uneducated soul like me.
It's just one of these days you feel like reading a bunch of RFCs for fun.
Like DEFLATE. https://tools.ietf.org/html/rfc1951
PHP is basically, like, baby Java
So Twitch VODs are deleted after 60 or whatever days, right? And the chat data goes along with them?
But people upload those VODs to other places?
What if there was a way to capture that chat data and play it back afterwards along with the VOD from elsewhere?
Nope, apparently I can't get the magic incantation working to log in the way I want due to two factor auth. Ah well.
On the other hand, Twidere exists and even though it appears to be unmaintained it continues to work as long as neither Twitter nor Android change too much. Might be worth a go, if only push notifications worked as well too.
Sigh, just went on the birdsite again and even being anywhere near uspol right now is like the opposite of what seems good for me now. Why do I keep doing this?
Oh right because Twitter DMs are actually a surprisingly good medium for communicating with certain internet acquaintances.
Sigh. Almost like I should have a write-only client for that.
Actually, this thinking out loud brings up an interesting point—much of where development platforms are moving today is to help making things more rapidly, going towards higher and higher levels of abstraction. Not like it hasn't been that way ever since computing came about, but for some reason when you are actually amidst it you notice it a lot more.
This feels like it should be a blog post, not a toot thread (I'm not a fan of them either), so I'll cut it here though.
Of course that also means additional responsibilities and that much of your code will be dedicated to layering over the nitty-gritty of the platform, but I can't say it's not enjoyable.
Though it seems that Google doesn't want you to work in a low level way like that, what with Jetpack and all the auxiliary libraries that help you forget about the fact that there's a lot of SQLite stuff going on under the hood. I suppose it's good if you're in a hurry, but I feel that I'm not.
Also I'm working on a native Android app, and after having worked in the web for so long, though I can't yet tell whether it's subjectively better, it's definitely different but not in a bad way.
Now I understand Marco Arment's shifted stance after having worked on Tumblr and then went to iOS. The web has its advantages but with native it feels like you're much more in control of things, if that makes sense.
Y'know what's fun? Having your phone bitrot away its disk encryption key and then not unlocking because sysui decides that the passcode is correct but can't unlock the encryption key and failing miserably.
How's your morning been going?
I'm here for this. Yay European timezones.
Watching #AGDQ2020.
The puns are peaking.
