Conversation

Notices

1. Embed this notice
   Renaud Chaput (renchap@oisaur.com)'s status on Monday, 08-Jan-2024 04:51:28 JST Renaud Chaput

   in reply to

   • Merry Jerry 🎄🎅🕎⛄️❄️

   @jerry allowing easier migrations between instances is on the roadmap, and this iwll most probably includes migrating (part of) your posts

   • Embed this notice
     Merry Jerry 🎄🎅🕎⛄️❄️ (jerry@infosec.exchange)'s status on Monday, 08-Jan-2024 04:51:29 JST Merry Jerry 🎄🎅🕎⛄️❄️

     in reply to

     Since it has been the source of some confusion:

     Infosec.space is running on much, much smaller hardware than Infosec.exchange. Both have ample room for substantial growth, however. I continue to identify and address bottlenecks, but things are quite stable now.

     You can download your posts by clicking the “request archive” button at the bottom of the settings, import & export page.

     Mastodon does not support importing posts. Setting up shop on a new instance is starting over from a posts perspective. Your followers will transfer automatically and you can refollow based on an export of your follows (not automatic). There are some GitHub issues open against mastodon to support this, but it’s not on the roadmap as far as I am aware. Firefish and iceshrimp do support important posts, but the software is much less refined than mastodon is. Infosec.town and fedia.social both run this software.

   • Embed this notice
     Merry Jerry 🎄🎅🕎⛄️❄️ (jerry@infosec.exchange)'s status on Monday, 08-Jan-2024 04:51:30 JST Merry Jerry 🎄🎅🕎⛄️❄️

     Hi all. Just a reminder that I created infosec.space for people who do not want any interaction with threads.net, while infosec.exchange will let members choose whether to interact with threads or not*.

     • blocking another instance at the account level is not as effective as instance level blocks, but still good at preventing access to posts.