Search results

After reviewing FEP-5624: Per-object reply control policies and GoToSocial's interaction policy spec, I find myself leaning toward the latter for long-term considerations, though both have merit.

FEP-5624 is admirably focused and simpler to implement, which I appreciate. However, 's approach seems to offer some architectural advantages:

  1. The three-tier permission model (allow/require approval/deny) feels more flexible than binary allow/deny
  2. Separating approval objects from interactions appears more secure against forgery
  3. The explicit handling of edge cases (mentioned users, post authors) provides clearer semantics
  4. The extensible framework allows for handling diverse interaction types, not just replies

I wonder if creating an that extracts GoToSocial's interaction policy design into a standalone standard might be worthwhile. It could potentially serve as a more comprehensive foundation for access control in .

This is merely my initial impression though. I'd be curious to hear other developers' perspectives on these approaches.

3
0

New blog post!

This time I talk about the two recent migrations I did with my data:

I migrated my main VPS from a US based VPS provider to @hetzner because I want to have my stuff in Europe.

The second one was the migration of this exact account from which I send this toot, I moved it from Fosstodon to my own GoToSocial instance which I am self-hosting on that Hetzner server.

I hope you will find it useful!

https://stfn.pl/blog/69-migrating-servers-migrating-instances/

#gotosocial #fosstodon #fediadmin #hetzner

0
0

My relay instance for the evolved in a great way - more than 120 instances are already connected to boost your posts across the Fediverse.

If you're running / , , or any other software on the protocol that supports relay instances - feel free to join the relay! Hopefully also supports relay services soon! Of course is supported (for IPV6 only instances).

fedi-relay.gyptazy.com

Screenshot of the overview page of fedi-relay.gyptazy.com showing more than 120 connected instances for a federated network within the Fediverse.
0
0
0
0

Если видите, что я на вас не подписался - без паники.

Я тут подписался на небольшую группу человек и тестирую свой личный инстанс. В теории может получиться так, что я найду тут какие-то недостатки и либо создам инстанс на другом поддомене или поеду на какой-то другой публичный.

Но если всё пройдёт удачно - я сделаю "миграцию" сюда, вас сюда автоматически подпишет (если вы были подписаны на @skobkinAlexey Skobkin), да и свои подписки оттуда я тоже перевезу.

#warning #announcement #log #GoToSocial #test

0

🏕️ my adventures in #selfhosting - day 132 (awesome allies edition) 🎬

ICYMI: last week I installed and began tweaking my own #PeerTube instance – thanks to the ease and awesomeness of #YunoHost: @eleElena Rossini on PeerTube

https://videos.elenarossini.com/a/ele/video-channels

Now, the BEST resource there is for anyone who wants to self-host their own PeerTube is this video by @paigePaige Saunders on @fedihostFediHost Video : https://video.fedihost.co/w/63AETQCcEMigzTHTmTu2Wn?start=0s

I wish I had watched it on day 1 (instead of day 3 of my journey), as it would have saved me A LOT of headaches.

The ENTIRE FediHost PeerTube channel is full of gems and I would highly recommend subscribing to it.

And now off I go print out the latest version of the script of my Fediverse video... my interns arrive in a few hours for our first production meeting. Exciteeeed

#EleFediVideos #MySoCalledSudoLife

0
0

Now that #GoToSocial v0.19.0 is out, we're going to start the process of transferring our coding workflow from Github over to #Codeberg (@CodebergCodeberg.org), to get away from Microsoft's endless parade of crapola.

This means that some time in the next week or so, we will "lock" the Github repository so that only superseriousbusiness.org members can create new PRs and issues etc (similar to what we do when we're on holiday).

Then, we will migrate the repository over to Codeberg, using Codeberg's migration functionality to keep issues, pull requests, comments, etc intact.

Once we've validated that everything is in order, we will mark the Github repository as a read-only mirror of the Codeberg repo, and start using Codeberg for issues, pull requests, CI/CD etc.

To avoid breaking people's automated builds that rely on that Github repo, we are planning to keep it as a read-only mirror for a while (eg., 6 months or so, not sure yet) . At some point though we will fully remove it, to avoid contributing our code to Microsoft's "ai" garbage. But we will warn in advance about this so that people can update their scripts and stuff in time.

There will probably be some turbulence in our CI/CD pipelines and workflow and whatnot during this transition period, but nothing that should affect end users of the software: releases up to v0.19.0 will remain available on Github and Docker as normal, and snapshots should remain up to date on our Minio S3 bucket and Docker.

We're looking forward to the move, and to putting the sloth in its new home and seeing it wander around sniffing the furniture and exploring :gtspat: Thanks for reading!

0

🏕️ my adventures in #selfhosting - day 126 (good luck charm edition) 🍀​

Good morning Fedi friends!

Yesterday I flew back to Paris and I’m spending the week at my in-laws' with my extended family… my little one still has one more week of school holidays. Working is a little difficult with so many people around (especially children) but I have a lofty goal for today: upgrading my VPS and installing #PeerTube.

The 22nd of the month has been my good luck charm in my self-hosting adventures. I installed #GoToSocial (this account) via #YunoHost on December 22nd, 2024. I successfully installed #Ghost on my Ubuntu VPS with command lines on February 22, 2025. Because of that, I will be saving 30€/month…

So in the spirit of #FOSS exploration, I find it fitting to upgrade my VPS today on April 22… and - my oh my! - install PeerTube via YunoHost… so that I can self-host my upcoming videos about the Fediverse.

The children are playing in the garden and I have about 30 minutes to do all that. Wish me luck!

#MySoCalledSudoLife

0
0
0

If you run a single user #GoToSocial instance, maybe you would like to get more toots about a specific subject in your timeline.
#FediBuzz relay could help you. You can subscribe to a specific hashtag fake-account and then receive toots it re-toots.

more info here https://relay.fedi.buzz/

For example, you can follow @tag-gotosocial#gotosocial

0
0

A bit of an unusual tutorial on today. It’s an interesting project so there is a lot of explainer mixed in while I waited for the accounts to migrate.
GTS gives you this preview of a future when move command is in the AP spec and you can migrate any account into any other account.

From: @fedihostFediHost Video
video.fedihost.co/w/i2AGvZc69g

0

This #GoToSocial account has become a step-by-step tutorial in how to self-host the publishing platform #Ghost (and troubleshoot issues) 😆

If you're not interested in my messages on the subject, I will be using a new hashtag #EleSelfHostsGhost so you can just mute it.

I'm a little late to the party because everything is now set-up and running smoothly:
✅ I manually installed Ghost on my Ubuntu VPS
✅ I imported all the old posts and media: https://news.elenarossini.com
✅ I installed #Apache to use #Varnish cache and changed the cache's maxAge so that a bit of traffic wouldn't overwhelm my VPS
✅ I published and shared on Mastodon a new blog post: https://news.elenarossini.com/what-im-up-to-march-april-2025-edition/ Thanks to Varnish and the maxAge cache tweak, the VPS withstood the "Mastodon stampede" (the post had made it to Explore!)

So far so good.

👹 but when I tried to send that blog post as a newsletter to just 210 people, #Mailgun immediately flagged me as a spammer and froze my account 😱

It took about 48 hours of back-and-forth emails with the Mailgun team to convince them I'm not a spammer and to get my account reinstated.

Now, why am I sharing all this?

In case you are also tempted to self-host Ghost, I found that the official Ghost - Mailgun documentation has little information available. But I discovered this super helpful post in the Ghost Forums and I will be trying this tweak to see if it makes a difference:

https://forum.ghost.org/t/unable-to-send-newsletter-with-correct-mailgun-api-keys/34186/6

And yes, I'm aware that if you sign up for my newsletter you will get an email with a warning "this message failed the domain authentication" (or something along these lines). Problem is, when I implemented a tweak, changing config settings, the alert went away but I saw a spike in activity in my Dashboard, as if I had sent 600 emails (I did not). For now I can live with the warning.

I appreciate Ghost's new implementation of a spam filter because around the same time I got really suspicious signups originating from the same domain.

Anyway after I change all this I will try to send once again my blog post as a newsletter.

Special thanks to my parents for looking after my little one so I can do all this while she's on a school vacation ❤️

0

👆 asking because Peertube itself doesn't feel very social, neither the web site nor app, and not great for discovery. It seems more like a platform for hosting videos and social aspects and discovery via other platforms might be better. But Mastodon is not great wrt federation of Peertube videos so... Is any other platform better?

0
0

New instance, new #introduction

My name is Mike (a.k.a. "shellsharks”) - I am a security researcher, #IndieWeb advocate, all-things #Fediverse convert and all around #tech enthusiast.

I write about #infosec, #technology and #life over at https://shellsharks.com

Here's some other stuff I like... #apple #sports #travel #battlestations #food #starwars #lotr #pokemon #gaming #space #fitness #nba #basketball #hiking #camping #music #coding #programming #cybersecurity


So what's going on with this instance? Is this my "main" presence or am I still on shellsharks.social? Fair question. The answer is, yes! This is a #GoToSocial instance, on a new fun, shiny, vanity domain. If it works out, I might end up moving all my activity over here and shutting down the Mastodon instance I have at shellsharks.social. Until then, I'm operating out of both spaces. This also means that for now, I haven't migrated my followers (or followed accounts) over here, so don't be offended if I haven't followed you back yet! I don't want to knock this fairly low-spec'ed instance over so I'm taking it slow with how I am using it.

Why am I doing this? Well for one main reason really, I wanted an instance where I could post more than 500 characters at a time. GtS gives me that, and much more. Bonus points for A. being less resource intensive than Mastodon (so cheaper to run), B. more customizable and C. I could get an even more ridiculous vanity domain.

So don't be surprised to see a lot more from this account than my usual @shellsharks account. If you'd like, you can follow me here for now. No worries either way.

See y'all around Fedi!

0

🏕️ my adventures in #selfhosting - day 104 (pride edition) 👷‍♀️

Good morning Fedi friends!

Aw pride is a powerful thing.

I'd like to think that I'm pretty zen and detached and successfully suppressing my ego... but when it comes to things I'm passionate about (read: tech, self-hosting) I cannot let things go.

I had a very very sweet shout-out on a Fediverse podcast last week... but said shout-out mentioned my self-hosting issues and that maybe self-hosting isn't for everyone. I felt that I had to correct the record (even if the mention came with the nicest intention)... because I have ZERO issues self-hosting #GoToSocial, #Friendica and #Pixelfed (thanks to the magic of #YunoHost). All my troubles had to do with #Ghost. (And Ghost is wonderful, it's not related to it, just external circumstances).

So, determined to defend my honor (ha!) on Friday I achieved the impossible: all by myself, following guides I found online, I managed to install #Apache and #Varnish on my VPS and connected Varnish to Ghost. My site was already fast, now it's BLAZING fast.

So I'm giving it another go, moving from Ghost (Pro) to my self-hosted Ghost installation. I turned off subscriptions on https://blog.elenarossini.com... next step is disconnecting the subdomain DNS (a CNAME record) from Ghost... and redirecting traffic to my new blog (https://news.elenarossini.com).

I know how to code things in NGINX for the redirect to work (I think, via guides I found online).

My big question is: how do I tweak my old DNS records for https://blog.elenarossini.com so that NGINX on my self-hosted site https://news.elenarossini.com will correctly pick up the traffic requests? Do I need to set up A and AAAA records for the subdomain blog to point to my VPS with the self-hosted Ghost blog? Any advice would be greatly appreciated! 🙏​

Oh and I learned my lesson and - unlike last time - I am making big changes on a Monday morning, when I have the whole workweek ahead of me (instead of a Friday afternoon 1 hour before picking up my child from nursery school). You live and learn! 😅​

#MySoCalledSudoLife

0

Galera linda e novinha (ou até mais antiga) do ! Seguem algumas dicas para melhorar sua vida por aqui :blobBone_dance:

:alerta: Se achar longo, leia as 3 primeiras dicas e salve. Mas LEIA o resto! :raposa: É bem importante :alerta:

:sm64_1: Cuidem da sua bio :blobBone_jump: Coloquem uma foto, escrevam um textinho, mesmo que simples. Botem boas informações como gostos e hobbies no perfil :ablobcatbongokeyboard: E uns toots (postagens) não fazem mal a ninguém, assim sai confundido com um 🤖

:sm64_2: Faça a sua em um toot :catjam: Essa é uma boa maneira de conhecer novas pessoas e interagir no ! O pessoal tem costume de dar :boost:, então aproveite!

:sm64_3: O é construído com interações, então se quiser ser seguido é bom interagir 🦜 Mais em (por @pancho) bolha.one/@pancho/113135497401

:sm64_4: Deixe sua linha do tempo bem viva! Além de seguir pessoas, é bom seguir e usar por aqui :pusheenBounce: Conheça as várias @TagsBR que acontecem semanalmente :ablobcatdj:

:sm64_5: Também que podemos seguir e interagir com timelines de outras instâncias também. Muito bão isso :nkoHappy:

:sm64_6: Abaixo (links) tem ótimas listagens de instâncias brasileiras (e até latino-americanas). Lembrem que SEMPRE pode mudar de servidor. Seu servidor, sua instância faz MUITA DIFERENÇA na sua experiência aqui no . Se está achando sem graça ou só não está gostando tanto, pense em mudar :bugcat_sweat:

Ainda mais importante para quem está na mastodon.social que é a mais genérica possível. Quando mudei, tudo mudou :blobBone_bounce:

social.harpia.red/notice/AfFmR (por @kariboka) e brasil.rednet.social/ (por @santiago)

:sm64_7: Use e teste diferentes aplicativos para ver o que mais gosta. Já usei vários e recomendo o @moshidon para (feito pelo @lucas_na_ursal). O , por exemplo, permite interagir com a timeline de várias instâncias. Depois coloco uma recomendação aqui de um app para iOS.

:sm64_8: Postou uma imagem, um gif ou um vídeo, coloque o texto alternativo. Isso é bem importante e valorizado por aqui. Eu mesmo só dou boost se tiver texto alternativo. Outra dica importante é descrever sua foto e capa do perfil :chick_writer:

:sm64_9: O na web também pode ser acessado com interfaces alternativas como: elk.zone e phanpy.social. Experimente, o é cheio experiências diferentes e proveitosas! Um mundo novo :ms_cat_smile:

:sm64_1: :sm64_0: Além da você também podem seguir interagir com comunidades do Lemmy (Forum ou Reddit daqui) ou de grups. Basta seguir que vai aparecer na sua timelime e marcar em um toot para aparecer por lá ou para quem segue. Exemplo @ fediverso@a.gup.pe ou @ internet@lemmy.eco.br. Pode achar outras comunidades aqui:

Lemmy Brasil: lemmy.eco.br/communities
Forum da Ayom.Media:forum.ayom.media/communities
Forum da Bolha.us: bolha.forum/communities

:sm64_1: :sm64_1: O tem muitas alternativas descentralizadas, então explore 🚀 Só alguns exemplos abaixo, existem muito mais🤘

Microblog: , , , , .
Foto: @pixelfed.
Blog: , @writefreely
Video: @peertube
Forum/Reddit: Lemmy

:sm64_1: :sm64_2: Outras dicas importantes:

Pelo @diegopds bolha.us/@diegopds/11305822732

Pelo @augustocc social.br-linux.org/@augustocc

O que acharam? Bão? Aberto a sugestões e melhorias :catroll:

Amplificações sempre ajudam :boost: :caramelo: :raposa: :ablobcatbongopost:

0
0
0
0

Good morning Fedi friends!

It's been 99 days since I started self-hosting my own Fediverse instances. Crazy how time flies!

I've been a bit absent from here this week because I started exploring the world of #PeerTube from the POV of a creator.

I just set up my own account on #MakerTube - so that I can write a guide that is accessible to many (as opposed to skipping this step and going straight to self-hosting).

Anyway, here is my PeerTube account: https://makertube.net/a/elena/video-channels

I have been able to follow it from #Mastodon and #Friendica without a problem, but I keep getting an error message when I try to subscribe with my #GoToSocial username. The exact message: "Cannot fetch information from this remote account." Does anybody have the same issue? (as in: people on GoToSocial, can you subscribe to PeerTube channels?)

Wishing you all a lovely day 🌞​

P.S.: about to go offline for the rest of the day because... there's no pre-school in France on Wednesdays and the garderie keeps my little one up until 12:30. So apologies in advance if I'm slow to reply to messages.

#MySoCalledSudoLife

0

Hey there! For those new to DMV.Community or Mastodon in general, I can also be found in a few other places and I run some other services.

I run a instance for photo sharing at pixtagram.social. My account there is @jcrabapple@pixtagram.socialJason Crabtree .

I run a instance called The Shrediverse at shrediverse.net. It's like a lightweight Mastodon that you can use with most Mastodon clients. This instance is generally music-focused and anyone can join. I have an account there @jcrabapple@shrediverse.net where I share music-related stuff.

I have a personal blog at cool-as-heck.blog and a music blog at blog.shrediverse.net. I haven't been very good about updating them lately but I'm trying to be better about it. 😄

I also maintain two Mastodon frontends that anyone can use: elk.dmv.community and phanpy.dmv.community.

If you'd like to donate to support hosting costs for DMV.Community you can do so at my Kofi page: ko-fi.com/jcrabapple

Peace, love, and tacos 🌮

0
0
0
0
0
0

Hi everyone! We just made a bugfix release v0.18.2 of #GoToSocial:

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.18.2

If you're updating to this version from v0.18.0 or v0.18.1, it's a very easy update with no db migrations or config file changes :)

If you're updating to this version from a version before v0.18.0, please follow the update instructions from v0.18.0, but replace 0.18.0 with 0.18.2 throughout. Be aware that the update to 0.18.x contains some very long migrations. Please do read the notes carefully.

This is hopefully the final bugfix release of 0.18.x, so you can stay on this one for a while while we work on v0.19.0 :)

Thanks for reading, happy slothing, acab, death to fascism, and if you have money to spare this month go donate it to these folks who need help :gtspat:

Hello nerds, another #GoToSocial bugfix release :) Turns out 0.18.2 wasn't the last one after all.

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.18.3

This one fixes a bug with domain subscriptions with orphan adoption, which could cause entries for the subscription to not be created. An important bugfix for island networks that rely on allowlist subscription(s) to keep everyone in the network on the same allowlist(s).

Also small wording changes on the frontend, and a fix for an issue that could cause error messages to be swallowed on startup.

If you're updating to this version from v0.18.0, v0.18.1, or v0.18.2, it's a very easy update with no db migrations or config file changes :)

If you're updating to this version from a version before v0.18.0, please follow the update instructions from v0.18.0, but replace 0.18.0 with 0.18.3 throughout. Be aware that the update to 0.18.x contains some very long migrations. Please do read the notes carefully.

0

🏕️ my adventures in #selfhosting - day 89 ✨

Oh #PeerTube, you are making me do mental somersaults as I strategize about the best way to self-host my videos.

This newbie wants to ask: how many VPS’s are too many for someone who has little coding experience and has been self-hosting for just 3 months?

Fedi friends, I’m thinking of signing up for a THIRD VPS 😱

Why?

My current setup:

1️⃣ 5€/month Debian VPS with #YunoHost, where I’m self-hosting #GoToSocial (this account), #Friendica, #Pixelfed, #Fail2Ban and #LinkStack.
2️⃣ 5€/month Ubuntu VPS where I am self-hosting my (upcoming) #Ghost blog (this will make me save a ton, compared to my current Ghost Pro plan).

Back to PeerTube: I could easily upgrade my #Debian VPS and install it there - the costs would be minimal and I would double my RAM and storage. But I am afraid of PeerTube’s consumption when it comes to bandwidth. As in: if I upload a video that for some reason becomes really popular, or if a bad actor decides to DDOS my channel, would that take down all my other self-hosted Fediverse instances? Since they are on the same VPS?

I could limit potential issues by having a dedicated VPS just for PeerTube.

What would you do?

And do you have recommendations for Europe-based VPS’s with affordable plans? (aside from Hostinger) I was thinking of #Hetzner…

#MySoCalledSudoLife #AskFedi

0

It looks like there's something up with GtS v0.18.x on arm64 specifically, as a few people have reported issues with not being able to start GtS on arm64 devices like the RockPro64. We'll look into a fix :) In the meantime arm64 folks: better stay on v0.17.4 for now. But if you do have GtS v0.18.1 working fine on arm64, please let us know so we have the datapoints. Thanks!

Edit: it looks like this applies specifically to the RockPro64, weirdly enough. Other arm64 devices have been fine (thanks for the data points everyone).

Hi everyone! We just made a bugfix release v0.18.2 of #GoToSocial:

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.18.2

If you're updating to this version from v0.18.0 or v0.18.1, it's a very easy update with no db migrations or config file changes :)

If you're updating to this version from a version before v0.18.0, please follow the update instructions from v0.18.0, but replace 0.18.0 with 0.18.2 throughout. Be aware that the update to 0.18.x contains some very long migrations. Please do read the notes carefully.

This is hopefully the final bugfix release of 0.18.x, so you can stay on this one for a while while we work on v0.19.0 :)

Thanks for reading, happy slothing, acab, death to fascism, and if you have money to spare this month go donate it to these folks who need help :gtspat:

0
0

Hello everyone, after a week or two down the release candidate mines, we've emerged blinking into the light carrying with us #GoToSocial v0.18.0 Scroingly Sloth!

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.18.0

Please read the migration notes carefully for instructions on how to upgrade to this version. This version contains several very long migrations so you will need to be patient when upgrading, and backup your database first!!

Release highlights

  • Status edit support: one of our most-requested features! You can now edit your own statuses, and see instance edit history from other accounts too (if your instance has them stored).
  • Push notifications: probably the second most-requested feature! GoToSocial can now send push notifications to clients via their configured push providers.
    You may need to uninstall / reinstall client applications, or log out and back in again, for this feature to work. (And if you're using Tusky, make sure you've got ntfy installed).
  • Global instance css customization: admins can now apply custom CSS across their entire instance via the settings panel.
  • Domain permission subscriptions: it's now possible to configure your instance to subscribe to CSV, JSON, or plaintext lists of domain permissions.
    Each night, your instance will fetch and automatically create domain permissions (or permission drafts) based on what it finds in a subscribed list.
    See the domain permission subscription documentation for more information.
  • Trusted-proxies helper: instances with improperly configured trusted-proxies settings will now show a warning on the homepage, so admins can make sure their instance is configured correctly. Check your own instance homepage after updating to see if you need to do anything.
  • Better outbox sorting: messages from GoToSocial are now delivered more quickly to people you mention, so conversations across instances should feel a bit snappier.
  • Log in button: there's now a login button in the top right of the instance homepage, which leads to a helpful page about clients, with a link to the settings panel. Should make things less confusing for new users!
  • Granular stats controls: with the instance-stats-mode setting, admins can now choose if and how their instance serves stats via the nodeinfo endpoints. Existing behavior from v0.17.0 is the default.
  • Post backdating: via the API you can now backdate posts (if enabled in config.yaml). This is our first step towards making it possible to import your post history from elsewhere into your GoToSocial instance. While there's no way to do this in the settings panel yet, you can already use third-party tools like Slurp to import posts from a Mastodon export (see Slurp).
  • Configurable sign-up limits: you can now configure your sign-up backlog length and sign-up throttling (defaults remain the same).
  • NetBSD and FreeBSD builds: yep!
  • Respect users prefers-color-scheme preference: there's now a light mode default theme to complement our trusty dark mode theme, and the theme will switch based on a visitor's prefers-color-scheme configuration. This applies to all page and profiles, with the exception of some custom themes. Works in the settings panel too!

Thanks for reading! And seriously back up your database.

Hiya, we just did #GoToSocial bugfix release v0.18.1, which adds ETag cache control handling to /robots.txt to make it easier for crawlers to tell which instances they should + shouldn't be indexing.

You can find the release and update notes here:

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.18.1

If you're updating to this version from v0.18.0, it's a very easy update with no db migrations or config file changes :)

If you're updating to this version from a version before v0.18.0, please follow the update instructions from v0.18.0, but replace 0.18.0 with 0.18.1 throughout. Be aware that the update to 0.18.x contains some very long migrations. Please do read the notes carefully.

Thanks!

0
0
0
0

Hello everyone, after a week or two down the release candidate mines, we've emerged blinking into the light carrying with us #GoToSocial v0.18.0 Scroingly Sloth!

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.18.0

Please read the migration notes carefully for instructions on how to upgrade to this version. This version contains several very long migrations so you will need to be patient when upgrading, and backup your database first!!

Release highlights

  • Status edit support: one of our most-requested features! You can now edit your own statuses, and see instance edit history from other accounts too (if your instance has them stored).
  • Push notifications: probably the second most-requested feature! GoToSocial can now send push notifications to clients via their configured push providers.
    You may need to uninstall / reinstall client applications, or log out and back in again, for this feature to work. (And if you're using Tusky, make sure you've got ntfy installed).
  • Global instance css customization: admins can now apply custom CSS across their entire instance via the settings panel.
  • Domain permission subscriptions: it's now possible to configure your instance to subscribe to CSV, JSON, or plaintext lists of domain permissions.
    Each night, your instance will fetch and automatically create domain permissions (or permission drafts) based on what it finds in a subscribed list.
    See the domain permission subscription documentation for more information.
  • Trusted-proxies helper: instances with improperly configured trusted-proxies settings will now show a warning on the homepage, so admins can make sure their instance is configured correctly. Check your own instance homepage after updating to see if you need to do anything.
  • Better outbox sorting: messages from GoToSocial are now delivered more quickly to people you mention, so conversations across instances should feel a bit snappier.
  • Log in button: there's now a login button in the top right of the instance homepage, which leads to a helpful page about clients, with a link to the settings panel. Should make things less confusing for new users!
  • Granular stats controls: with the instance-stats-mode setting, admins can now choose if and how their instance serves stats via the nodeinfo endpoints. Existing behavior from v0.17.0 is the default.
  • Post backdating: via the API you can now backdate posts (if enabled in config.yaml). This is our first step towards making it possible to import your post history from elsewhere into your GoToSocial instance. While there's no way to do this in the settings panel yet, you can already use third-party tools like Slurp to import posts from a Mastodon export (see Slurp).
  • Configurable sign-up limits: you can now configure your sign-up backlog length and sign-up throttling (defaults remain the same).
  • NetBSD and FreeBSD builds: yep!
  • Respect users prefers-color-scheme preference: there's now a light mode default theme to complement our trusty dark mode theme, and the theme will switch based on a visitor's prefers-color-scheme configuration. This applies to all page and profiles, with the exception of some custom themes. Works in the settings panel too!

Thanks for reading! And seriously back up your database.

0
0

:liberapay: liberapay.com/f0x

I host the pixie.town Mastodon and Matrix servers (and a bunch of other smaller services).

I also work on a variety of projects, like the ActivityPub server and a new ActivityPub client , as well as a bunch of other projects you can find at git.pixie.town/f0x

social.pixie.town is co-moderated by @thufie:thufie: דגל שכור 🏴 :contains_thc:, she has a liberapay at liberapay.com/thufie

0
0

Hello #Fediverse and Happy New Year!

I'd like to mark the start of 2025 with the first message from my self-hosted instance. You may already know me as @_elena@mastodon.social. Well, now I also run my own #ActivityPub microblogging server, thanks to the magic of #YunoHost and #GoToSocial (and #Phanpy, which I'm using to compose this).

I registered this domain – aseachange.com – a looooong time ago but never did anything with it. It was the very first domain name I ever bought, even before securing elenarossini.com (!!!). It was so long ago, but I remember I was inspired by Beck's album Sea Change. seachange[dot]com was taken, so I grabbed Aseachange.

I absolutely love its meaning of profound transformation and I think it's PERFECT for my self-hosted #Fediverse instance and what it represents: independence, empowerment and digital sovereignty.

Ever since setting it up, I've been feeling joyful and hopeful. Everytime I look at myself in the mirror, I think: I'm in control of my own social media platform. And it feels SOOO GOOD.

What do I have in store for 2025? I plan to use this account to post messages about #selfhosting, learning #Linux, privacy and digital sovereignty.

I will also keep posting from my Mastodon account because you don't give a Lamborghini to someone who just passed their driver's license. I barely know what I'm doing here, so I feel a lot safer (for now) keeping my mastodon.social account as well... In case anything goes wrong here. Better safe than sorry!

So, this is my #Introduction and if you've read as far as here I just want to thank the Fediverse for being so amazing and allowing me to connect with people on my own terms. And thank you Fedi people for being so generous and supportive with your superb advice and kind words.

This is a really magical, special place.

Happy New Year, everyone!

Good morning Fedi friends!

So yesterday I posted the first public message from my self-hosted instance, powered by #GoToSocial (see above).

✨ The good 😊

I was able to export the list of accounts I follow on Mastodon and import them very quickly and easily into the new instance. Ditto for my Mastodon block list. The whole thing took less than 2 minutes.

☔️ The puzzling* 🤔
*I'm not gonna call it "the bad" since I'm LOVING GtS so far

I tagged my Mastodon handle but it didn't turn into a hyperlink and thus I didn't get the mention/notification on Mastodon. I also included the URLs of a couple of my websites (without the https://) and they were rendered in the post as regular text, not hyperlinks.

So, let's try again – for the purposes of testing:
@_elenaElena Rossini ⁂
https://elenarossini.com (this time I included the https)

If you're curious about #selfhosting, #YunoHost and/or #GoToSocial, feel free to reach out and ask Qs.

Wishing you all a lovely day!

0

Hello #Fediverse and Happy New Year!

I'd like to mark the start of 2025 with the first message from my self-hosted instance. You may already know me as @_elena@mastodon.social. Well, now I also run my own #ActivityPub microblogging server, thanks to the magic of #YunoHost and #GoToSocial (and #Phanpy, which I'm using to compose this).

I registered this domain – aseachange.com – a looooong time ago but never did anything with it. It was the very first domain name I ever bought, even before securing elenarossini.com (!!!). It was so long ago, but I remember I was inspired by Beck's album Sea Change. seachange[dot]com was taken, so I grabbed Aseachange.

I absolutely love its meaning of profound transformation and I think it's PERFECT for my self-hosted #Fediverse instance and what it represents: independence, empowerment and digital sovereignty.

Ever since setting it up, I've been feeling joyful and hopeful. Everytime I look at myself in the mirror, I think: I'm in control of my own social media platform. And it feels SOOO GOOD.

What do I have in store for 2025? I plan to use this account to post messages about #selfhosting, learning #Linux, privacy and digital sovereignty.

I will also keep posting from my Mastodon account because you don't give a Lamborghini to someone who just passed their driver's license. I barely know what I'm doing here, so I feel a lot safer (for now) keeping my mastodon.social account as well... In case anything goes wrong here. Better safe than sorry!

So, this is my #Introduction and if you've read as far as here I just want to thank the Fediverse for being so amazing and allowing me to connect with people on my own terms. And thank you Fedi people for being so generous and supportive with your superb advice and kind words.

This is a really magical, special place.

Happy New Year, everyone!

0

With this release, Ivory now UNOFFICIALLY supports additional fediverse platforms such as GoToSocial, IceShrimp.NET. I've tried these platforms with mostly success.

The better the Mastodon API support on your platform, the better your experience will be. Obviously, platform specific features like emoji reacts or reply controls aren't going to be available. Still nice!

Edit: SNAC and Hollo work as well now!

tapbots.social/@ivory/11411043

0
0
0
0