marcelcosta
@thraeryn Interesting!!
I am also worried (as every fedizen) about instance inestability. However, proposed solutions tend to focus on technological approaches and less on social/community approaches. While they are complementary, I think that we should work in building communities and workflow protocols that don’t rely in a single person (or too few people) to run their instances.
The Embodiment of RED
cybre.space is closing, after five years. link
thraeryn.net is closing, after five years. (It was much smaller; my reasons are different, but related.)
I worry that we'll see more of our already-precious islands in this FediSea closing their doors soon. It's fun, as a hobbyist, to spin up one's Very! Own! Social! Media! and invite one's friends to come play. There's pride in knowing you runs a reasonably tight ship, respect from every peer that chooses to federate with you.
It seems we're hitting the point where some of our hobbyists are burning out. Whether it's because of too many or too few users, some of us are just worn down from running those ships.
I know I'm about to propose more work, probably unpaid, but our community should strongly consider coming together to create a simple playbook for opening, running, closing, and transferring the administration of instances. Not just Eugen, or the folks that run or contribute to various projects and code bases; all of us, as many as we can get.
It's time to think about codifying how instances are run, at least loosely, so we have a shot at keeping our version of the Fediverse alive. The version run by our friends and peers, not by a slew of BigCorps and opportunistic start-ups. The version that's trying, even if it fails, to be an inclusive community.
senooken JP Social is a social network, courtesy of senooken. It runs on GNU social, version 2.0.2-beta0, available under the GNU Affero General Public License.
All senooken JP Social content and data are available under the Creative Commons Attribution 3.0 license.