Hi all, I need your opinion on a thing: Another internal #Smithereen update. I hacked my web framework to have the ability to stream my responses as they're rendered — this results in a slight performance improvement, especially for HTML as rendering templates isn't exactly instant. Tweaking the way comments are displayed in the feed and in profiles in #Smithereen. 3 last top-level comments are shown, you can click the bar above them to load more, and you can load individual threads. There are also these subtle dots on hover to help you determine the depth of each comment. (not fully done yet) I'm getting better at making CSS cascade the exact way I need. Also I've finally gotten PostCSS to optimize my styles exactly like I want. Still, as someone who has mostly made mobile UIs (Android) up until starting this project, desktop ones have an overwhelming amount of detail! Screens are larger, layouts are denser, and there's often MUCH more information and controls displayed at once. Oh and mice are capable of hovering over things. An internal #Smithereen update: I replaced the org.json JSON library with gson. It allows for somewhat cleaner code with its JsonElement base class for everything, supports serializing/deserializing Java objects directly (will come in especially handy for when I'll be making the API!), and preserves a sane order of keys in objects. Yes, that last part is very important because it hurt to read the mess that came out of org.json. Oh and I also made a pull request to gson: https://github.com/google/gson/pull/1900 Everyone was asking for this feature. Since 2008. SINCE 2008!!! But it was never added. The first iMac had two headphone jacks, so modern iPhones having none are merely compensating for that. And now I think I'm done and I can say that these features are enough for the first beta release. Everyone is welcome to host their own #Smithereen 0.1 instance, try it out, and report any issues. Get it here: https://github.com/grishka/Smithereen
Show previous comments
@grishka #Smithereen update: Mastodon's "PropertyValue" custom profile fields are now displayed in profiles. Today's #Smithereen updates: - Account bans. Very simple feature. An admin or a moderator can ban any local account and set a message that will be displayed to the user. - The JS and CSS files are now generated as part of the main maven build so I no longer have to commit a bunch of minified CSS every time I add a style. #Smithereen update. There's now an "about this instance" page like the one Mastodon has. There's also new fields in the admin panel, for a short description and for policy/rules. And another one. Implemented /api/v1/instance and /api/v1/instance/peers endpoints that fediverse crawlers use. (to be clear: there's currently no client API in Smithereen, and when there'll be one, it won't be compatible with Mastodon clients) The only kind of platforms this world might need more of is the ones at which trains arrive. Hey @Gargron, could you please update https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/ with the now required Digest header? The form. I don't remember what it was like in the before-microblog era, but after-microblog it was right below that block header, like this. There was also an intermediate form where it said "X posts" next to "Wall" in the header itself. And it's also supposed to be collapsible. This is a neat feature. @grishka@mastodon.social maaan! That really looks alike now! Do you think #smithereen is already ready for some daily fediverse activities? Meanwhile Twitter's Bluesky is still obsessed with impractical P2P protocols and end-to-end encryption. It's as if they're trying to reinvent the wheel, but the result turns out square, and they assume it'd somehow be better. Imagine them spending all this time implementing #ActivityPub into Twitter instead.
Show previous comments
@grishka @activitypub If you link to the actual conversation then everyone can see our replies too. https://twitter.com/grishka11/status/1391893118648193035 @grishka @activitypub And to be clear, we've been working on this since 2013, long before bluesky (or activity pub!) was a thing. It takes a long time to get privacy and security right, especially in a P2P setting. |