My own priorities are
  1. reviewing and merging some these very kind pull requests
  2. some kind of editing - something like a 5 minute window for edits
  3. better notifications
  4. growth hacks so we can get a more active community: sat referral program and tips
I've also begun thinking about how to best decentralize SN. Open sourcing was a step in this direction but it'd be better if users could run their own SN node. There are a number of stumbling blocks here but for longevity/trust, it's something I'd like to do.
What we'd mostly end up needing is for the backbone of SN to be an append only log relay that's effectively a dehydrated version of the SQL DB that we'd rehydrate on each node (using something like https://github.com/fiatjaf/nostr or https://github.com/dominictarr/scuttlebutt).
reply
Decentralizing SN I think should be a priority above all front-end, nice-to-have like features. I would happily run a SN node at home, especially if you could get it added to Umbrel's app store.
reply
Definitely an important feature but also the most difficult to implement. It'll need to be designed/researched first which is something I can do in parallel to developing little nice to haves.
reply
Check out ActivityPub protocol for the decentralization (federation) of SN, that would open floodgates for folks from PeerTube, Mastodon, Pixelfed, Lemmy... :)
Separately you could make SN into an App on Umbrel (it's fairly simple, just wrap in a container and add config to Umbrel) to run well with your Umbrel Bitcoin Core & LND and then that would be hats down truly amazing solution.
reply
Oh and also figuring out the UX around some kind of better client-side cache invalidation so the recent/main page posts don't require a manual refresh.
reply