Gregory's Server@cblgh I've seen similar thoughts from folks! Having instance-only posts seems particularly appealing. I need to investigate what is required to shift us over, but we should put this up to a vote soonish!
|
5 comments
 @flip @cblgh Yeah that's definitely worth considering. There's a bunch of features available besides local only posts that factor into this too—I originally didn't want to move to a fork specifically because of the potential maintenance/upgrade overhead and not being able to switch back, those are valid concerns!  @somnius @flip maybe @darius can chime in with his thoughts on the current status of Hometown's maintenance & such? afaik, Hometown is explicitly about minimizing the difference between upstream & its changes–if only to reduce the maintenance burden. i think local-only (and the speculative future feature of neighbourhood-only posting) would be a big boost, esp. given the situation today wrt online safety  @cblgh @somnius @flip Maintenance is going apace, although the latest Mastodon 3.3.0 introduced a ton of regressions and conflicts and I've been too distracted (uhhh being American) to put the time in to fix them right now. That said, I usually update to the latest upstream within a week of release. In terms of what would happen if a feature was adopted upstream with a different implementation -- I would certainly try my best to provide a migration path. |
@somnius @cblgh I just went to check the GitHub issue for local only posts again... it’s been open for two years, no clear indication, afaict, if it’ll happen upstream
I’d like to avoid a situation where we switch to hometown and then the feature we needed lands upstream and we have to switch back and the content it incompatible
That being said, I also don’t want us to live without a feature we’d love