Email or username:

Password:

Forgot your password?
Nolan Lawson

Pinafore development has slowed down because I've been focusing on other things, like my personal life. But I'm starting to ramp up a bit now and have been fixing some bugs recently.

Part of it has been me stepping away from social media in general (I don't post as much as I used to) and from open-source software (it became a source of guilt and dread, so I dialed back on it). Cooking, biking, books, and video games have been a more fulfilling use of my time recently.

7 comments
Nolan Lawson

Honestly, Pinafore is the only interface I need for Mastodon, and the main one I've used since I started developing it. I know the Mastodon frontend has tons of features Pinafore doesn't support (trending hashtags, server announcements, profile editing, etc.) but I just haven't felt hugely motivated to add those.

Nolan Lawson

I'm conflicted between wondering if this is me just being chauvinistic, or if it's actually a low-key value-add for Pinafore that it doesn't have a million bells and whistles (which would probably make it slower, etc.). Maybe some users like a more stripped-down interface where the cheese doesn't move much?

Nolan Lawson

Originally, my goal with Pinafore was to build what I thought was the "ideal" Mastodon UI from a technical perspective. Fast, accessible, offline-first, single-column, true virtual list, etc. Since then, the Mastodon frontend has caught up in a lot of ways (e.g. single column), so these things are less of a competitive advantage.

Nolan Lawson

I also saw it as a way to push the limits of what the web could do. However, I've become a bit chastened and disillusioned about this. For instance:

- Pinafore doesn't have nice animated transitions like native apps do. The web still sucks at this.
- Offline support is almost impossibly hard given Mastodon's API. The main benefit of IDB right now is low memory usage.
- PWAs haven't come far enough. Pinafore isn't listed in app stores, so it "doesn't exist" for most users.

Eugen Rochko

@nolan What about the API makes offline support impossible?

Nolan Lawson

@Gargron I maybe overstated my case. A lot of it is not Mastodon's fault but just how hard it is to write offline-first apps in general.

When I worked on PouchDB, we had a whole sync protocol between the client and server that dealt with versioning, conflicts, etc. You just called `db.sync()` and you were done. I don't expect Mastodon to add this, but it's just an example of the kind of thing I miss from the PouchDB world.

charlag

@Gargron @nolan you don't get what happened while you've been offline. I was burned by it before with Tusky. You have a list of posts in db but you can't just show them from db, some of them get deleted or favs etc

Go Up