pinafore VS spec

For Windows, Whalebird is your go-to since it's in the MS Store. Most of the stuff I've found online as suggestions for Windows are web apps like https://pinafore.social/ or https://elk.zone. Personally, I just use the advanced web view. I need the columns.

https://pinafore.social/

Resilient Web Design, a PWA book by Jeremy Keith:

Pinafore - Alternative web client for Mastodon, focused on speed and simplicity.

Which instance are you on? Mastodon is decentralized, there may be servers that are overloaded whereas other are fast. Like email.

I haven't noticed any big differences in speed, i use both Mastodon for iOS and Pinafore (https://pinafore.social/ ), a PWA. Just add it to your homescreen and it will behave like a native app (and sometime in 2023 Apple has said they will add push notifications to PWAs).

I continue to see people stumble at mastodon resource requirements when setting up their instance, but I fail to understand why everyone is going for a mastodon instance for their personal use.

I am running https://github.com/superseriousbusiness/gotosocial on a micro instance, probably using 100M ram, with a 30M sqlite database.

True, I don't have all features. It is pure backend, but I can use https://pinafore.social/ as web client and https://f-droid.org/en/packages/su.xash.husky/ as Android app. It implements a good chunk of the Mastodon API. I also use it from Emacs with mastodon.el.

Took me 35 minutes to setup. It runs as a single binary from systemd. Most of the jail features enabled. Not even a system user (DynamicUser).

Mastodon != Fediverse.

i use https://pinafore.social on windows fine.

There's ucan too, which fills some similar-ish roles. It's definitely not quite as comprehensive & featureful as ocapn, but worth mentioning. https://ucan.xyz/

Thanks for the mention! Capyloon (https://capyloon.org) had a grant from Protocol Labs (the IPFS stewards) in 2022 so we focused quite a bit on that indeed. We learned a lot - especially about the maturity and usability of the IPFS stack.

I'm still very bullish on the dWeb pieces: content based addressing, UCANs (https://ucan.xyz/) for distributed auth, new web app models (https://hackmd.io/@robin-berjon/tiles) to create an ecosystem that is not locked by centralized app stores.

There's a lot to do, all contributions are welcome (frontend, device ports, platform apis...). We have a Matrix channel (https://matrix.to/#/#capyloon:matrix.org) and you can try desktop builds easily following the steps at https://github.com/capyloon/nutria#quick-start

https://ucan.xyz - similar technology

..which builds on https://ucan.xyz/ for auth. I’m also curious to learn what Chatternet does differently, and whether that’s necessary.