 I'm not very good at designing UIs. But I've found this rather exhaustive palette for VK's old website 🤔 It's gonna be interesting to try to adapt this to green-ish color I'm going for in #Smithereen. I never quite liked what I'm getting with PostCSS color functions. As a bonus: since everything is already in variables, it'd take marginal effort to make an "exactly like VK in 2011" theme with these colors unchanged. Why is there no open-source reimplementation of all the proprietary parts of the macOS userspace? #Smithereen web UI is so fast that my browser doesn't have enough time to show a progress bar when you navigate between pages 🤔  One thing I find mildly annoying in #Stargate is their computer UIs. These are clearly designed with a mouse in mind. But almost none of their computers have mice. Instead, they, by the looks of it, just type random crap on the keyboard, as if they have Vim for their window manager. Their interactions with computers look VERY unnatural. And besides, I know how hard it is to make animations. Yet their very specialized software is crammed with unnecessary animations. It also beeps too much. And, I mean, good luck clicking these buttons at the top right without the mouse. Their status bars are useless. And, no, you don't need "STATUS: ACTIVE" in every window. It's not helpful. Not aligning the shapes in icons with the pixel grid is the worst crime in the modern UI design. A #Stargate episode got me thinking about how much of our modern technology I could reproduce if I suddenly ended up in a less advanced civilization. I'd certainly have to reinvent a lot, but I'd probably build a working computer in the end. Out of relays. Because transistors require highly pure silicon and clean rooms, and besides, I just suck at chemistry. Oh, and if they do have computers already, internet would be very easy to make. It'd be better than ours by skipping IPv4, too. Cloudflare was down today. And this was a friendly reminder about why this centralization of the internet is a very very bad and dangerous thing. Don't use Cloudflare. So I went ahead and replaced the template engine in #Smithereen. Had to remove many weird hacks both in code and in templates. Works fine so far. And a bit faster, too. See my thread for details: https://mastodon.social/@grishka/104489466413781940 Isn't it just amazing when you want to take a peek at the documentation for the template engine you're using and you're greeted with this?! UX aside: how does one request a desktop website on iOS? Of course you tap the "aA" icon for that. Isn't that obvious?! And if you want to find something on the page, that's under "share". And I hate Safari even more. Yes, I did put an svg into an <img> tag. Yes, this is a retina display. No, this doesn't mean you should rasterize the infinitely scalable svg at 1x and THEN draw it on the 2x screen. Sigh. It is now possible to run #Smithereen in Docker. Also: the installation process has become easier — you no longer need to run any SQL queries manually! I guess I can now add Docker to my résumé? Oh and also. Because the JNI library isn't supposed to change very often, if at all, I've built it for everything I can so you don't have to. Probably need to figure out Windows at some point. #Smithereen update. If a comment gets deleted and there are replies to it, this no longer breaks the thread. In this particular case, instead of deleting the DB row completely, I null most of it but keep id and reply key. And the #ActivityPub object remains fetchable but returns a Tombstone with replies & inReplyTo. Speaking of replies, my posts didn't have that collection for some reason, now they do. #Smithereen update. At this point, I can finally consider likes to be done and fully functional the way I want them. They're better than Mastodon's, too — they *should* be consistent across instances, that is, as long as other instances send them LD-signed. Same thing about replies. I now forward activities to make sure every instance that has the top-level post of a thread has a complete representation of the thread itself.  cc @Gargron please do the same with threads. It's very harrowing seeing incomplete conversation threads and having to open the thread in the separate tab to get a full picture. #Smithereen update. I've refactored the hell out of the most crucial federation-related part — #ActivityPub inbox. This is going to allow me to do all kinds of things, like forwarding LD-signed activities to other instances for the sake of data consistency. Does this 5-parameter generic feel like proper enterprise-grade Java yet? :D  @grishka the way I do it in littr.me: 1. Aggregating recipients: 2. Disseminating to local recipients. #Smithereen update: L I K E S!!1 |
Gregory's Server
:thonking: 🤔