The alpha version of @gotosocial now has support for allowlists.
Allowlists automatically prevent federation with all other servers, except those that the admin has added to their allowlist. (Traditional blocklists work the other way round, allowing all federation unless a server is blocked.)
Allowlists bring more safety but also reduce reach, and that's why it's up to each admin to decide whether to use them.
📌 If there's someone wondering where I am at, currently I am more active at @hnb which on my own #GoToSocial solo server. I thought I would keep posting here too but it did not turn that way...for now.
:blobfox3c:
Working on some better language tag support for #GoToSocial, including being able to set preferred server language(s). It won't do much yet but it will be important down the line.
Looks like my #gotosocial is way faster now that it's running on new storage (and RAID1 instead of single drive now). But: somehow not all servers seem to have noticed that my instance is back 🙃
@ajroach42 Sounds solid to me. #GoToSocial also looks cool too though I haven't looked too hard at it. If I was looking at a server for just me or my immediate family I would probably seriously consider that over anything in the masto or pleroma/akkoma realm.
Seems like a good choice to focus on a small number of distinct options for fedi hosting.
Placeholders for unknown media attachment types are merged into #GoToSocial and will be in 0.13.0 :)
This means that if someone posts a media attachment of a type your instance doesn't recognize or can't process (funky video types, pdfs, image types we don't support yet), or if there's a network issue fetching a piece of media, it will no longer just be thrown away.
Instead you'll be served a link to the remote URL for that piece of media, so you can open it in directly in your (mobile) browser.
The next time you refresh that status (2hr cooldown), your instance will try again to fetch the piece of media, and automagically update the status if it succeeds.
We fixed an issue where remote accounts that were suspended via targeted suspensions in the admin API could be later marked as unsuspended. This means that the suspended account had all their relationships / media / statuses etc deleted, as normal, but these might end up being repopulated later on if you interacted with the account again.
If you suspended any remote accounts from your instance via a targeted suspension in the admin settings panel, since 0.12.0, you may need to suspend these accounts again after updating to this release.
Note: This issue only affects remote accounts that were suspended in that particular way (targeted via the admin API). Domain blocks (and accounts suspended as part of a domain block) are not affected by the bug, nor are local accounts suspended via the admin API.
This week I boosted posts from #GoToSocial and #Akkoma instances and followed someone on a #Funkwhale instance all from my #Mastodon instance, as if they were all Mastodon posts and accounts.
The other day I was messing around with the lightweight alternative to Mastodon called #GoToSocial (currently in Alpha).
Anyway I registered a silly little domain name (https://bits.lag.tf) and have now been running it for a while in production on a tiny Alpine #Linux container on my home server.
I thought I'd put it out there if anyone is interested in a test account DM me your email and desired username or fill out this form and I'll set you up.
@Susan60 Hi, I apologize. I've decided to indefinitely shut down the autobooster since I realized that this is a really ugly workaround (there's just no way as far as the software I used goes to even determine whether it's a reply or posted by a user that has #nobot in their bio) for #GoToSocial's lack of support for relays as well as #guppe and #chirpsocial not federating well with GTS (I can't follow groups from there).
@scanlime It seems they took down the instance hosting the follow bot (which is kishinjou.chaotic.ninja), and there aren't any follow bot in their Misskey at makai.chaotic.ninja (probably because they don't really need to there, the only reason why the follow bot was created according to mima was that #GoToSocial doesn't support relays and therefore it's pretty difficult to get your instance connected with plenty of other servers) so that reason no longer applies.
I'm not sure what you mean by "edgelord"? I've had nothing but good interactions with people in chaotic.ninja. And this is just nitpicking from me at this point, but #touhou is not an anime. Or at least officially isn't...
It was a lot of fun :blobcataww:
There's a good potential: simple to install&configure, setup instance like you need 🤩
Just it's still in alpha and not yet able to migrate account 🙃
I'll be patient and it'll stay on my server as an experimental thing, a toy to play with 😊
(still a lot of thing to learn, reverse proxy I'm looking at you!)