
40y mold | ♿ | 🇩🇪 | IT & engineering | metalhead | furry | ADHD mess of niche interests | nsfw 🔞 no minors
I've noticed a lot of fedi operators will run Matrix homeservers as well, that's probably the "most correct" option for an IM platform to go with the archipelago but I'm sure someone's mentioned it by now.
I'll be watching that RSS feed and I might join later on! This is a really interesting project!
i was just listening to someone talk about matrix. i'm thinking we should actually take a good look at it because in principle, it fits the model. we're only on discord atm because of the extremely low barrier of entry.
imo keep the discord, even if you do eventually start a matrix. just make it very limited scope. the discord solely exists to help people navigate the process stuff and, find an instance, and get on.
you wanna talk about something else? website's right over there buddy.
now that i think about it. i'll be pushing to find someone willing to maintain mod stuff in the discord server even if we end up using something else for most of the admin stuff. i'm sure there are plenty of people already in the admin group who are still going to be using discord on a daily basis anyway so why not?
Are you okay with people sharing this on other sites (bsky, mastodon, etc) so other people looking for a new internet home post cohost can see it? or do you not want all that visibility right now?
i think we want to stick with cohostians for the bootstrapping phase so that we know we have people coming from a common culture because that culture is so different from everywhere else. eventually we will want to open it up to more.
I'm personally not opposed to talking about the project between a group of a few friends, etc., but yeah we probably don't want this making the rounds on other platforms just yet. Once things are a little more established, we can start thinking about sharing with a wider audience imo
I was thinking of posting it elsewhere so other cohostians who aren't on here as much after The Announcement can see it.
What will the barrier to an account look like and will it have an easy user interface like here?
Is the goal for this something like forum platforms of old? This sounds a lot like ezboard and stuff
Not quite, there is a separate effort for that on a diff discord though (like, specifically, to make a 00’s era forum)
sorry if this is a silly question, but will this have a twitter/mastodon-style interface with publicly visible likes and followers and numbers etc or is it more of a cohost-style "blogs with shares and comments and a few social features" thing? i don't know enough about activitypub to know if all of those publicly-visible numbers are an unavoidable part of the protocol or if that's specifically just how mastodon chooses how to do things. i know the post says it has "avoidance of dark patterns" but i can't see anything more specific than that.
we haven't formalized it yet, the assumption we are working under is that any instance wanting to be a member is going to, as much as possible, hide the instance-wide and network-wide (non-tag) feeds, and hide all visible metrics
Seems like a complicated way to build an rss reader. What are the benefits of this vs a traditional rss reader?
This is not an RSS reader. It's interconnected social media sites.
how are the members of the "central decision making body" chosen
in the discord server, there is an accepted proposal listed that defines this - far too long to put in a cohost comment section verbatim unfortunately but to summarise:
membership is voluntary and open to anyone meeting any of the following conditions:
after formalization (tbd on what constitutes "formalization"), conditions change to:
FYI- The discord link says it's an invalid invite (for me at least), and I never got a confirmation email after signing up for the newsletter.
Fixed the discord; we just switched it over to a community server and it invalidated the existing invite links.
Why a rule against having a federated timeline? Either I don't understand the thought behind this or there's a misunderstanding about what that means
Edit: also I run gotosocial for my self hosted account and definitely recommend it for new folks, it's still very early software but it's infinitely easier to install and deal with for a small instance especially if you're just hosting yourself.
I think it’s an effort to not recreate The Cohost Global Feed. I know the mastodon local and global feeds are the originals but . Admittedly I could not express the distinctions between the two offhand.
That’s good to hear about gotosocial! The very techy nature of this project has been. Very intimidating to me to be honest!
I replied below to @atomicthumbs so I don't wanna just repeat it but it addresses the local/global feed thing a bit.
My theory is that a huge part of Mastodon/Fediverse social volatility comes from the fact that instances are force-connected in an inorganic fashion that arises from the structure of the network instead of from user interaction. cohost having to make the entire tag system less powerful to stop harassment stemming from the global feed tag adds a bunch of data points.
Maybe I'm misunderstanding the other half of the structure then because if it's all allowlist only setup and an island where the members are following each other, then the federated feed would only ever be the other people on the island network, which...seems like a pretty good thing to have!
Unless you just mean that that federated feed shouldn't be viewable by logged out users? Or maybe the structure is less of a true island than I understood?
Edit to add: If the problem is people INSIDE the network are using the feed to harass people, I would hope the rules around this project would require them to do something about that from a moderation standpoint and that none of the member instances would be at too big of a scale that this moderation wouldn't be feasible. I actually think it'd be a good idea to have some sort of user cap for member instances because the worst thing a fedi instance can do is get big.