My next big plan for Hometown is a clear and safe migration path BACK to vanilla Mastodon. That way there's not a huge commitment to trying it out, and if something happens to me or the project, you can always go back to regular Mastodon.

The hard part is figuring out what to do with local-only posts when an instance moves back to Mastodon. I wrote down my current thoughts on how this might work, both on short-term and long-term solutions:

github.com/hometown-fork/homet

@darius is there a way to do the DM solution such that a move back to hometown again restores them?

@bcj if there were, I wouldn't implement it. too confusing for users. even the DM thing might be too confusing, I'm not sold on that either

@darius I'm not super familiar with the specifics, but if you give the local posts a url that doesn't actually match any routes, it shouldn't be fetchable. e.g., /status/username/local-10999876/. But it exists on the server, and so is accessible via API.

The weak point is I believe some API calls are open to the public and it may slip out.

@tedu It's the latter I'm worried about, which is why v1 is just going to be full deletion.

@Cito there are fairly comprehensive instructions on the wiki! as long as you are self hosting it should be doable. I'm happy to help, too

Sign in to participate in the conversation
Friend Camp

The decentralized web is about trust. You should only join Friend Camp if you personally trust Darius Kazemi with your social media data. You probably only have that level of trust if we are IRL friends or have been internet friends for a long time. Generally speaking this is a small, closed community. In the end, Darius is the arbiter of what is allowed here. If you don't have a good idea of the kind of behavior that flies with Darius, again, you probably shouldn't join this instance. In the interest of specificity, we do have a code of conduct and privacy policy which you should read. Friend Camp features several modifications that were requested by our users. * you can log in via any subdomain, which means you can log in to multiple accounts in the same browser session (for example, log in once on friend.camp and then as another user on alt.friend.camp) * they are no longer called "toots", they are now "posts" * if you have a locked account and you get a follow request, a reminder appears under your "post" button (on normal Mastodon mobile it is otherwise buried in a sub-menu and you might not see it for a long time) * the emoji dropdown is a neutral smiley face instead of the cry-laughing smiley @mentions are rendered as "@user" for a Friend Camp user and "@user@domain" for remote users. This helps clear up when you follow two people who have the same username on different servers. * there is a "never ask me again" checkbox on the confirmation for clearing your notifications -- more info here * When an mp3 link is in a post, we also embed an inline mp3 player. git commit here * 500 characters of profile text git commit here, requested by @deerful Important Bit from the Privacy Docs: If you want decent privacy (the info doesn't leave this server), the only way to do that is to set your account to private, only accept friend requests from other friend.camp users, and only ever @ mention other friend.camp users. Once you start talking to people on other servers, all bets are off. Any private message you send to someone on another server could be looked at by the admin of a different server. This is kind of like email: if you are on a private email server, and you send an unencrypted email to a gmail account, congrats, Google now has the content of that email. But also, you do this every day, so, hey. The internet! Our beautiful icon is based on photo3idea_studio from www.flaticon.com, licensed CC 3.0 BY. It has been modified by @casey@friend.camp!