onnes

Furry Physicist and Lead Engineer

  • they/she

Avatar by @stratica
NSFW: @darkonnes


atomicthumbs
@atomicthumbs

still thinking about Website League (It's like a confederation of websites in here)


atomicthumbs
@atomicthumbs

so here's the deal. i'm working on learning how to use docker to get Pixelfed up and running properly, so I can build a place for cohost's photography community. at least one friend is building a place for therians and other creatures, which I am planning to federate with.

This would be an island - it's a separate federation, not directly connected to the Fediverse at large. this allows post-cohost culture to remain isolated from mastodon so we don't piss people off

Important Points

  • I am not in charge of it and don't want to be in charge of it
  • Character limits as large as possible - it's not microblogging
  • probably no CSS crime support unless someone figures out how to implement it, sadly
  • Intended primarily for Cohost users and those who liked Cohost's style
  • Allowlist-only: a site has to intentionally join the island, and others must choose to federate with it.
  • Isolated from the Fediverse, to allow people to continue posting as they have here without getting in fights for not conforming to the Fediverse/Mastodon culture at large
  • Single base set of community guidelines, based off Cohost's (maybe with some modification)
  • To federate, you must base your server's rules on those community guidelines and enforce them. No Racists Or Chuds Allowed
  • We will need some kind of decision-making apparatus (this one's hard)
  • Single-user instances can federate with us, and with the Fediverse at the same time, as long as they agree to follow the rules and be chill
  • Ideally, accounts are approved manually, to avoid spam and try to keep bastards out
  • No minors (sorry kids)
  • No Mastodon (the software) instances allowed currently, as I am told there's currently an unreported bug that would mildly compromise the island's isolation ("if an instance in your federation has a user who boosts an external post, and the instance that external post is on does not have authorized_fetch enabled, it can result in a fat boost which includes the post contents inline and this will end up showing up to other instances even though the instance it came from isn't on their allowlist")
  • There are many other kinds of software that do what Mastodon does; it's heavyweight and stuff like GoToSocial is easier for smaller instances

ironically i think this is gonna need a website


You must log in to comment.

in reply to @atomicthumbs's post:

asking mostly because that's what i've already got set up, i've used a *key derived single user instance as well but unfortunately settled on mastodon because even if it's heavier the majority of the wider fediverse is seen through the keyhole of how mastodon renders it (i.e. i can upload higher resolution images if i set my instance or a different piece of software like pixelfed to do so, but mastodon will always crunch it down before an end user sees it, bleh)

but that's not the goal with the smaller subset of allowlist servers anyhow :3

i'm curious to know if/when mastodon would be usable for this in the future, though!

also i'm not 100% on its use for some other software, as it's largely a workaround for issues with mastodon being dumb for file storage and retrieval across many servers, but i would recommend checking out/emailing to inquire about jortage for communal sharing of storage costs if you hadn't heard of it https://jortage.com/

Yeah i'm in the same boat, spun up my own single-user Mastodon instance because that's what I'm accustomed to and a lot of the 3rd party client ecosystem only interfaces with it.
But I'll survive if I need to spin up a GoToSocial / make an actual account somewhere else, it's fine. More website = more good.

this sounds like an interesting experiment. we set up our own gotosocial over the past few days and it was surprisingly simple to do, not much more to it than setting up our own git server. it even supports allowlist-only mode which is handy for such a concept

i would petition going case by case on what constitutes a "single-user instance" mostly because as a plural system we have/will end up with multiple users in the computer sense on our instance. that's probably still single-user as far as your concept is concerned.

however i dont think i'd be opposed to just setting up a second gotosocial on the same computer i put the first one on for this purpose, so it's not a big deal to me. really i might prefer that.

to anyone else who has set up a mastodon server already and is like "oh god another one?"- I getcha. lemme reassure you that gts is soooo much simpler to set up than mastodon its probably not as bad as you're worried about. the main downside is the selection of clients on desktop, but it's serviceable.

at least one friend is building a place for therians and other creatures

i'm interested. i don't know any community of therians or creatures outside of cohost and i'd love to stay in touch

Single-user instances can federate with us, and with the Fediverse at the same time, as long as they agree to follow the rules and be chill

limiting this to single-user feels overly restrictive? "no open membership" is fine and appropriate but it seems unnecessary to require e.g. a polycule who all want the same network overlap to each spin up their own instance. being allowlist-only already means a node can just be defederated if it turns into a problem.

i think this is more for "if you want to federate with both the League and the wider Fediverse at the same time" - single-user instances can do that, multi-user sticks to the allowlist

I like this idea more because I think it'll be a bit more resilient than this place ultimately turned out to be even before it went under. Just hoping the culture doesn't come to put cohost on too much of a pedestal or try to cling too hard to an imagined past, but that's not a given.