Search

Items tagged with: GoToSocial

Hello everyone!

Here's version 0.20.2 of #GoToSocial; it's another bugfix release!

codeberg.org/superseriousbusin…

If you're updating to this version from v0.20.0 or v0.20.1, it's a very easy update with no db migrations.

If you're updating to this version from a version before v0.20.0, please follow the update instructions from v0.20.0, but replace 0.20.0 with 0.20.2 throughout. Be aware that the update to 0.20.x contains some potentially very long migrations. Please do read the notes carefully!

Release highlights:

  • Roll back to using name property instead of summary for alt text (for now anyway), due to compatibility issues with *oma, *key, and Iceshrimp.
  • Stub authorize_interaction to avoid surprising 404 when trying to do a remote interaction.
  • Fix issue that was causing emojis not to download properly.
  • Add optional build tags for reduced binary size.
  • Fix some swagger docs issues.
  • Various other fixes + performance tweaks.
  • Dependency bumps.

Thanks for reading! Have a good week!


v0.20.0 Sinister Sloth 😈 - superseriousbusiness/gotosocial

Here's version 0.20.0 of GoToSocial, **Sinister Sloth**. It's been a long summer of gently poking and prodding at the sloth's tummy and sides to make xem giggle.
Codeberg.org
#GoToSocial

How Hubzilla 10.6 b0rked its own forums

Just because it works under your very limited and controlled lab conditions, doesn't mean it will work just as well under real-life conditions.

A few may remember the summer of 2024 when (streams) rolled out FEP-171b. It broke federation in every imaginable way because, as it turned out later, (streams) suddenly confused the many different IDs it had to juggle. Granted, the byproduct of trying to fix this was Forte, the first Fediverse server software to provide nomadic identity via nothing but ActivityPub.

Now Hubzilla rolled out FEP-e232. And there's breakage again. Not quite as badly, but in places that really hurt.

So the talk of the town in the Fediverse is Mastodon 4.5 introducing quote-posts. (Mastodon 4.5 allegedly introducing quote-posts to the Fediverse, and how that's wrong, is another story.)

Interestingly, almost at the same time, Hubzilla 10.6 was rolled out. Money quote from the announcement:

  • Implement FEP-e232 (object links) for quote posts


FEP-e232 Object Links in practice usually = "quote-posts like Misskey" = linking to the original with "RE:" before the link.

Apparently, rather than what Hubzilla had been doing since 2012 when it was still Red. What Friendica has been doing since its own inception in 2010. Namely insert a dumb copy of the quoted post into the quoting post.

While (streams) and Forte have been supporting FEP-e232 under the bonnet for quite a while while still quote-posting with dumb copies, Hubzilla has decided to go all the way and replace the old-fashioned Friendica way of quote-posting entirely with the Misskey way that's all the rage in the Fediverse now.

Yes, this has its advantages. If the original is edited, then the edit (in theory) is reflected in all posts that quote-post it.

But here on Hubzilla, this switch causes trouble.

Mastodon rolled out rendering support for Misskey-style quote-posts before rolling out quote-posts themselves, so those Mastodon servers that can't render these quote-posts are hopelessly outdated.

Hubzilla, on the other hand, rolled out Misskey-style quote-posts with version 10.6 while 10.4 and older can't even render Misskey-style quote-posts, not even when they come straight from a *key. In this regard, it would have been smarter to first make sure that Hubzilla renders this kind of quote-posts, then wait for a few minor releases and then change the way Hubzilla quote-posts.

You may see this as just a minor nuisance. But on top of that, it breaks Hubzilla's forums.

See, Hubzilla's forums are based on quote-posts. You start a new thread by DM'ing to a forum, and the forum will automatically share (quote-post) your start post to all forum members. If it's a private, limited-access forum, only the forum members are permitted to see the post with your quoted post in it.

I guess it's kind of obvious that this can only work by quote-posting a dumb copy of the start post unless a few more stops are being pulled.

Now, however, forums on Hubzilla 10.6 quote-post start posts by linking to the original. Remember that the original is a DM to the forum. As in only the forum is permitted to see it. You can click the link to the original all you want. But unless you run the forum, Hubzilla will not let you see it, not even with all the OpenWebAuth magic sign-on that you have on yourself as a Hubzilla user. In fact, I'd be very worried if I could see it now.

If there was even only one active forum on one of the two public hubs that run development versions, this critical bug would have popped up earlier and been fixed before it would have hit a release. But apparently, nobody is crazy enough to run a forum on a dev-grade hub, not to mention how few active Hubzilla forums there are in the first place. Seriously, I wonder if there's any feedback coming from the two dev hubs because I never see any hit the Support Forum. Does it all go straight to Framagit?

Good thing hubzilla.org is still running Hubzilla 10.4. hubzilla.org is not only the official Hubzilla website, it's actually a Hubzilla hub itself. The official Hubzilla website is built on a Hubzilla channel, using the Webpages app. And hubzilla.org is home of the Hubzilla Support Forum. It would have been a disaster, had this forum been broken, too.

I guess there's a hotfix due now, even if it means reverting FEP-e232 support (although changing the permissions of a DM to a forum channel would do the trick, and looking at how (streams) and Forte do it would be even smarter). And I hope it'll come before hubzilla.org is upgraded to 10.6.

By the way, while it's at it, maybe Hubzilla could also permanently set that GoToSocial/Mastodon flag that allows being quote-posted. I mean, if you come to a place that has been able to quote-post for a whopping 13 years, that can quote-post any public content from anywhere in the Fediverse with zero resistance, and that has no control over whether or not your stuff can be quote-posted (other than not posting in public), it's safe to assume that you're okay with your stuff being quote-posted anyway.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Misskey #GoToSocial #Friendica #Hubzilla #Streams #(streams) #Forte #Forums #Groups #FediverseGroups #FediGroups #FEP_e232


fep/fep/e232/fep-e232.md at main

fep - Fediverse Enhancement Proposals
Codeberg.org
#friendica #Mastodon #hubzilla #misskey #GoToSocial #groups #Streams #fedimeta #FediverseMeta #longpost #CWFediverseMeta #CWLongPost #CWFediMeta #CWLong #Forte #Long #FediverseGroups #FediGroups #FEP_e232 #Forums

Hey folks, I'm considering to #selfhost my mastodon again, only I'm looking at #GoToSocial because it's soooo lightweight.
Is anyone using it full time of their instance? How does it feel admin/maintenance wise?

#Fediverse

#fediverse #selfhost #GoToSocial

as foretold for many months, now that v0.20.0 of #GoToSocial is released, we have removed our mirror of the code from Github, and removed all our other archived repositories from there as well

all development has been taking place solely on @Codeberg for months now, we just didn't want to remove our repo from Github immediately when we switched, since people might have been relying on it; so if you hadn't moved whatever mirrors / build systems etc to our codeberg repo yet, you ought to do it

#GoToSocial @Codeberg

Hi all, here's the third release candidate for version 0.20.0 of #GoToSocial

codeberg.org/superseriousbusin…

Couple little bugfixes for issues that were in rc2.

Please read the migration notes carefully for instructions on how to upgrade to this version.

If you're coming from v0.19.2 or below, please be aware that the migrations in this release are quite long (can take several hours, even!), as we had to rethread the entire statuses table to handle the new way we cache status threads (and to improve timeline performance). Please plan downtime accordingly, and most importantly hang in there and don't be tempted to interrupt the migration process!

What happened to rc3, you ask? It's a secret.


v0.20.0-rc4 - superseriousbusiness/gotosocial

Here's the third release candidate for v0.20.0 of GoToSocial. For instructions to update to this release candidate from versions < v0.20.0-rc1, see the [v0.20.0-rc1 release candidate notes](https://codeberg.
Codeberg.org
#GoToSocial

Hi everyone, here's the second release candidate for version 0.20.0 of #GoToSocial:

codeberg.org/superseriousbusin…

Compared to v0.20.0-rc1 there's been a few bugfixes, some docs changes, dependency bumps, and some improvements to migration performance (hopefully!).

Please read the migration notes carefully for instructions on how to upgrade to this version.

If you're coming from v0.19.2 or below, please be aware that the migrations in this release are quite long (can take several hours, even!), as we had to rethread the entire statuses table to handle the new way we cache status threads (and to improve timeline performance). Please plan downtime accordingly, and most importantly hang in there and don't be tempted to interrupt the migration process!

Thanks for reading, and enjoy your Sunday!


v0.20.0-rc2 - superseriousbusiness/gotosocial

Here's the second release candidate for v0.20.0 of GoToSocial. For instructions to update to this release candidate from versions < v0.20.0-rc1, see the [v0.20.0-rc1 release candidate notes](https://codeberg.
Codeberg.org
#GoToSocial

Lads lads lads lads!

Here's the first release candidate for v0.20.0 of #GoToSocial! If you're feeling bold, you can try this release candidate and help us find any lingering bugs before we release v0.20.0 proper!

codeberg.org/superseriousbusin…

Please read the migration notes carefully for instructions on how to upgrade to this version.

The migrations in this release are quite long (can take several hours, even!), as we had to rethread the entire statuses table to handle the new way we cache status threads (and to improve timeline performance). Please plan downtime accordingly, and most importantly hang in there and don't be tempted to interrupt the migration process!

Please also pay particular attention to the metrics changes, as we've significantly changed the way that metrics exposure is configured, so you will likely have to adjust your setup if you use GtS Prometheus metrics. For more information on the new way of doing things, look through this document: docs.gotosocial.org/en/latest/…

Release highlights

  • Big refactor of timeline code to use less memory and be (hopefully!) more responsive and less error prone.
  • Support for scheduled statuses!
  • Support for the focal point property on the frontend + over federation, so you can set focal point on your media and have it work properly!
  • Notifications when a status you've interacted with has been edited.
  • ListenBrainz widget on the frontend, so you can show off the music you've been listening to (docs.gotosocial.org/en/latest/…)
  • Instance info panel in the settings, so that non-admins on the instance can see which domains are blocked and explicitly allowed, and the reason why.
  • Bunch of new themes for profile views!
  • Config option to expose emoji endpoints without authentication -- useful for compatibility with some clients. Default value still requires authentication.
  • Footnotes in markdown!
  • Configurable thumbnail dimensions.
  • Federation of avatar + header image descriptions is handled now, both in + out of GtS.
  • The new hidesToPublicFromUnauthedWeb and hidesCcPublicFromUnauthedWeb are federated in and out now, allowing your instance and other instances that support these properties to transmit + respect preferences for the visibility of posts to render on the unauthenticated (public) web view of threads.
  • Support for avif file format.
  • JSON logging format, for easier log ingestion.
  • Atom and JSON feed support for RSS (not just xml).
  • Reworked metrics format, more + better metrics, and an importable example grafana dashboard.
  • Domain permission subscription retractions are now handled properly.
  • Probably a lot more! See below!

Thanks for reading!


v0.20.0-rc1 - superseriousbusiness/gotosocial

Lads lads lads lads! Here's the release candidate for v0.20.0 of GoToSocial! It's been a long summer of gently poking and prodding at the sloth, and she's finally getting ready to lumber out the door and say hello.
Codeberg.org
#GoToSocial

#GoToSocial #superseriousbusiness

Really wish I didn't have to say what I’m about to say, but here goes.
I am having serious doubts on whether hosting my own Fedi instance with #GoToSocial was really such a great idea. My instance still feels more like a deserted island in the middle of nowhere rather than part of a huge decentralized network with lots of activity.
My timeline seems incomplete compared to what I was getting when my account was on a larger Mastodon instance, although I’m actually following more accounts on here. Or so I thought, because actually, something seems to be very seriously wrong on my end when it comes to following accounts. Yes, I uploaded my following_accounts.csv file to this server, and yes, it did then start following these accounts as expected. Here's the weird thing though, if I look at the accounts that I’m following, a lot of them will have a status of „Follow request sent“. To be clear, these are unprotected, public accounts that anyone can follow, except me apparently. It's also not like this issue only shows up with one other instance or 2, it's a whole bunch of accounts across various different instances where this is going on. I can then retract the bogus follow request and then follow the account again, at which point it’ll correctly show that I’m following the account. As soon as I refresh or close and reopen that profile, however, I’m again seeing a pending follow request…
Also, pulling up account profiles only seems to work 25% of the time. Searching for a user like „someone@example.com“ will show the account, but without any profile info, as well as post and follower / following counts as 0. Opening the profile often results in nothing showing up for a few minutes, until the profile and posts eventually start to populate. I am also not finding anything in the GTS logs that would indicate issues with the config, no unexpected HTTP status codes, nothing which to me would indicate that there might be some issue in my config or network. I've been running hypebot and FediFetcher for several days at this point, but haven't really notized any significant improvements. So am I just being impatient / spoiled by the large Mastodon server I was on before, or am I right to be concerned?
#GoToSocial

Here it is, my new, self-hosted home in the #Fediverse running on #GoToSocial! This is really exciting stuff, now I’m truly living the Fedi spirit by supporting decentralization. If you're reading this and don't mind, I'd greatly appreciate a boost of this post to help my tiny new instance discover more servers. Thanks! #NewFedi #FediAdmin #Selfhosting
#fediverse #selfhosting #GoToSocial #fediadmin #newfedi

O vikendu jsem pokracoval ve zkoumani posunu Fediversa a dnes se mi povedlo deploynout Fedi server na lbc.wtf

Ma to hodne ostre hrany, ale v zasade se mi povedlo vsechno, co jsem chtel:
- smazal jsem bariery mezi webem, serverem a clientem.
- read-only pristup bez prihlaseni
- vlastni nalodeni
- podle otazek dostane novy uzivatel defaultni seznam sledovanych (zatim top ceske ucty).

Budu rad za vyzkouseni a feedback 🙏

#mastodon #it #server #web #gotosocial #phanpy #nextjs


LBC.WTF

Hipsterský průvodce po Liberecku
lbc.wtf
#Mastodon #server #IT #web #GoToSocial #nextjs #phanpy

Dear Fedi friends,

By now you might have seen the post announcing the release of my promotional video for the Fediverse. But in case you have boosts turned off, here we go: news.elenarossini.com/fedivers…

I posted about it this morning from my #GoToSocial account because I have a 5000 character limit there. And I had so many people to thank for their help. It really takes a village.

Thank you for all the wonderful feedback so far ❤️


📺 Introducing the Fediverse: a New Era of Social Media

A 4 minute video that aims to introduce the Fediverse to people not familiar with it
Elena Rossini
#GoToSocial

I've got a quick favour to ask. If you're reading this post on Mastodon (or the Fediverse), please click boost.

How come?

I recently moved across to my own self-hosted single-user server (using GoToSocial.org). For a bunch of reasons, including visibility across the Fedi, it would really help out.

#Fediverse #FediHelp #gotosocial #mastohelp

#fediverse #GoToSocial #fedihelp #mastohelp

The amazing feeling of discovering that The Archive Of Our Own has a character tag for "Fediverse Network/Mastadon Platform (Anthropomorphic)", followed by the disappointment of finding only a single #fanfic using that tag. I wanted to read a bunch of erotic #Misskey#fanfiction about all that forking! Maybe a #GnuSocial#Pleroma slashfic! Or some #GoToSocial and #Mastodon lemons. A #hubzilla and #friendica hurt/comfort fanfic anyone? C'mon, people. The fact a tag exists means we should use it. archiveofourown.org/tags/Fediverse%20Network*s*Mastadon%20Platform%20(Anthropomorphic)/works

Fediverse Network/Mastadon Platform (Anthropomorphic) - Works | Archive of Our Own

An Archive of Our Own, a project of the Organization for Transformative Works
archiveofourown.org
#friendica #Mastodon #pleroma #hubzilla #misskey #GNUSocial #fanfiction #GoToSocial #fanfic

#GoToSocial

Hi everyone!

We've just pushed a very important security bugfix release for #GoToSocial v0.17.3 and below:

github.com/superseriousbusines…

If you are running on GoToSocial v0.17.3 or below, you should update to v0.17.4 as soon as possible. It's a very small update from v0.17.3 -> v0.17.4 as it contains only some code logic changes, and no database migrations.

In short, when a dereferencing bug is triggered under a specific set of circumstances it can cause loss of account data on affected instances. It's a rare thing to be triggered, but when it does happen it really, really stinks, and necessitates restoring from backup or manually editing the database to get things working again. (It's not possible to access or tamper with data by triggering the bug, only destroy it.)

We'll release a proper CVE for this in a couple of days when admins and packagers have had a chance to update.

Please note that folks who are already on v0.18.0-rc1 or latest snapshots are unaffected and do not need to do anything, as the bug occurs specifically in v0.17.3 and below. This means if you prefer to update straight from v0.17.3 to v0.18.0-rc1 then that's also an option; you can follow the release notes for v0.18.0-rc1 in this case.

So! If you know folks on GtS v0.17.3 or below, please let them know that they should take action! Link them to this post if you want! And please boost for visibility :)

Thank you everyone! ❤ Computers!


Release v0.17.4 The Most Selective Sloth You've Ever Seen · superseriousbusiness/gotosocial

Here's version 0.17.4 of GoToSocial. This is a very important security bugfix release that addresses a dereferencing bug which, when triggered under a specific set of circumstances, can cause loss ...
GitHub
#GoToSocial

Hello nerds!

We've just created the first release candidate for #GoToSocial v0.18.0!

Adventurous admins can find the release candidate and upgrade instructions here:

github.com/superseriousbusines…

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!!

Thanks for reading! :gtspat:

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.
  • Better outbox sorting: messages from GoToSocial are now delivered more quickly to people you mention, so conversations across instances should feel 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.
  • Maintenance router will now be used while your instance is starting up / running migrations. It serves a nice status page informing visitors to wait while migrations complete. Less admin anxiety! Stuff is working!

Release v0.18.0-rc1 · superseriousbusiness/gotosocial

Here's the first release candidate of GoToSocial v0.18.0! Please read the migration notes carefully for instructions on how to upgrade to this version. This version contains several very long migra...
GitHub
#GoToSocial

the push notification code is now merged in #GoToSocial main, so that will definitely be in the next release :) we're mostly fixing bugs and stuff now, and polishing up bits and bobs, so expect 0.18.0-rc1 in a week or so probably! it should be a good one!
#GoToSocial

We're returning from our holiday and slowly homing in on maybe getting ready to consider looking at possibly doing another #GoToSocial release at some point soon or nearly-soon or whenever we feel like getting around to it.

Likely to be in the next release:

  • Post editing: already on main/snapshot.
  • Blocklist/allowlist subscriptions: already on main/snapshot. Check out the docs here -- docs.gotosocial.org/en/latest/… and here -- docs.gotosocial.org/en/latest/….
  • Push notifications: not on main yet but vyr has been working hard on this on a branch so we'll try to include it.
  • More bugs than ever before, more anti-capitalist homosexuality than you can shake a stick at, more torment collocated at the nexus.

2025 should be good!

Domain Permission Subscriptions - GoToSocial Documentation

None
docs.gotosocial.org
#GoToSocial

Myself and my good friend @bumble (who runs a variety of server types on the fediverse), are joining forces to offer #hosting for #GoToSocial servers.

It's early days but we'd be keen to hear from anyone who wants to try running their own GoToSocial but doesn't have the skill, want, or equipment to run their own server.

The aim is to simply charge for running costs for the server. We will not take any costs from this (unless we end up with hundreds of them!). We anticipate a basic instance for one user (or a small handful) will be 5 euros per month and the charge is month to month. You pay each month in advance, and can cancel any time.

All you need is a domain name (or a sub-domain of your existing domain). We can help with this, or help you buy one for a few dollars/euros. We will handle all admin of the server.

Initially we are only looking for a few people to participate. If you are interested send me a direct message.

#hosting #GoToSocial @bumble

#GoToSocial

#GoToSocial

Hoy hoy, just messed around and deployed this:

masto-fe.superseriousbusiness.…

based on the Iceshrimp standalone Masto frontend

You can log in to your #GoToSocial instance and use it like Mastodon :) All data is stored in the browser and on your own computer, masto-fe.superseriousbusiness.org doesn't store anything at all. It's like pinafore or semaphore in that regard.

I'll mess around with it more on and off as a hobby project, see if it can be customized + themed to feel a bit more like GoToSocial.

Thanks for trying it out!

Masto-FE (🦥 flavour)

masto-fe.superseriousbusiness.org
#GoToSocial

New blog post!

My GoToSocial instance has been running for more than a month now, and so I gathered the different bits and pieces of my experience running it, and made them into a blog post. I talk about resources usage, monitoring and backups.

Also, sharing the link on this fedi account running on the mentioned GTS instance is an experiment in itself, to see how my server will handle the traffic :ggsun:

stfn.pl/blog/54-administrating…

#gotosocial #fediadmins #blog

Screenshot of Grafana, showing six different graphs about the status of my server hosting the GTS instance.

Administrating my GoToSocial instance - monitoring and backup

The day-to-day tasks of a Fediverse instance admin
stfn.pl
#blog #GoToSocial #fediadmins

#GoToSocial #iceshrimp

#GoToSocial

Hi everyone! We've just made another bugfix release of #GoToSocial, version 0.17.2 Ridiculously Selective Sloth:

github.com/superseriousbusines…

The update fixes a couple small bugs around media processing and filter expiration, and adds media-image-size-hint and media-video-size-hint values to the config file.

Please read the release notes carefully when updating to this version.

Thanks for reading, and have a nice day! Or not, it's up to you; whatever you prefer! :catjam: :gtspat:


Release v0.17.2 Ridiculously Selective Sloth · superseriousbusiness/gotosocial

Here's bugfix version 0.17.2 of GoToSocial! If updating to this version from 0.16.0 or below, please follow the instructions for v0.17.0, replacing 0.17.0 with 0.17.2 throughout. ⚠️ Be aware that u...
GitHub
#GoToSocial

Hiya, we've just done bugfix release 0.17.1 for #GoToSocial.

github.com/superseriousbusines…

Fixes a bug in the streaming API that may have been causing problems for some clients, and adds alt-text for default avatar + header images.

Updating from 0.17.0 is very simple and quick, but if you're updating from 0.16.0 or below then please read the migration notes carefully and be aware of the big database migrations from 0.17.0.

Enjoy!

A young two-toed sloth gazing at the camera. From Wikimedia commons. https://upload.wikimedia.org/wikipedia/commons/b/b1/Two_toed_sloth.JPG

Release v0.17.1 Very Selective Sloth · superseriousbusiness/gotosocial

Here's bugfix version 0.17.1 of GoToSocial! If updating to this version from 0.16.0 or below, please follow the instructions for v0.17.0, replacing 0.17.0 with 0.17.1 throughout. ⚠️ Be aware that u...
GitHub
#GoToSocial

Sensitive content

#GoToSocial

Hi! Hi there! We've only gone and done another #GoToSocial release candidate innit mate!

github.com/superseriousbusines…

We fixed some small bugs, did a bunch of work around release note generation (not interesting for end users but tobi had fun), and documented GTS_WAZERO_COMPILATION_CACHE and nowasm.

Please read the migration notes carefully!

This is probably the final candidate before the real 0.17.0 release when we officially enter beta, we're all very excited here in the GtS treehouse! :gtspat:


Release v0.17.0-rc5 · superseriousbusiness/gotosocial

Here's version 0.17.0-rc5 of GoToSocial. We fixed a couple bugs! And changed some deployment stuff! And updated some library versions! Please read the migration notes carefully for instructions on ...
GitHub
#GoToSocial

Hiya, another day, another #GoToSocial release candidate:

github.com/superseriousbusines…

We fixed a couple small bugs around interaction accepts and rejects :)

Please read the release notes carefully, especially if updating to this release candidate from v0.16.0 or below! There are migrations!

If you're using SQLite on OpenBSD or FreeBSD, please take the release version with moderncsqlite in the name, as described in the release notes.

Thanks for reading and helping us find bugs! We're getting there 🙂

#GoToSocial

#GoToSocial @Erik @Adrian Roselli, pH0

Hiya! Third and hopefully final release candidate for v0.17.0 of #GoToSocial:

github.com/superseriousbusines…

Fixed a couple cheeky bugs related to status web views and pending replies not being marked pending correctly.

For instructions to update to this release candidate from versions prior to 0.17.0-rc1, please read the release notes for v0.17.0-rc1 carefully, but replace all occurrences of rc1 with rc3.

If updating from 0.16.0 to this release candidate, there are several config file changes and some very large database migrations that will have to run.

Thanks!

#GoToSocial

#GoToSocial

We're getting ready to start creating the #GoToSocial 0.17.0 release candidates, finally :)

We're now running this instance on the latest snapshot, to try stuff out and ensure it's working correctly. So far, it seems good!

To celebrate, here's a couple of MP3s, since it's possible to upload those now. Enjoy! And sit tight for the release candidates in a week or two ^_^



#GoToSocial

#Pachli 2.6.0 is now available. This version has a new "Suggested accounts" feature to find accounts to follow, improves filter support on #GoToSocial servers, makes parts of the UI more readable, and fixes several bugs.

See pachli.app/pachli/2024/06/27/2… for details.

Thank you to @mileskrell, @kallekn, and @bittin for their contributions to this release.

#AndroidDev


Pachli 2.6.0 released

Pachli 2.6.0 is now available. This release allows you to find new people to follow with a “Suggested accounts” feature, and has the usual bug fixes and other improvements. Read on for more details about these.
Pachli
#GoToSocial #androiddev #pachli @Kalle Kniivilä @Miles

Hi nerds! We've just released #GoToSocial version 0.16.0 Snappy Sloth into the wild. Look at it go! Climbing trees and all sorts, covered in algae, and #pooping once a week.

github.com/superseriousbusines…

Thanks to everyone who helped us comb the bugs out of its fur during the release candidate process. We hope the protein you gained from eating the bugs was reward enough.

As usual, when updating to this version (which you really should, because it's quite good), please read the release notes carefully, particularly the database migration notes; and make sure you don't interrupt the database migrations.

Ta!

Highlights of this release (nothing new since 0.16.0-rc1, just reiterating):

  • Sign up / registration: In this release, you can open your instance to new registrations (aka sign-ups) via the new signup page at https://[your-instance.tld]/signup. No more manually creating new users via the CLI :)
    Documentation here: docs.gotosocial.org/en/latest/…
  • Accounts overview for moderators: To support the new sign-up feature, and help instance admins to moderate, we made a new section in the settings panel where admins + moderators can get an overview of accounts, and filter by instance, status, and more. You'll find this new accounts view in the settings panel.
  • Totally reworked message delivery system and worker queues: We've completely reworked the way GoToSocial sends out messages to your followers and performs worker-related tasks; this should drastically increase the speed that outgoing messages are delivered, especially for users with lots of followers. It also paves the way for future work in terms of persisting worker and message queues over restarts.
  • Account mutes: The account mute API endpoints are now implemented, meaning you can put (timed) mutes of accounts in place, to hide statuses from specific accounts from your home timeline, and/or hide notifications from muted accounts.
  • Accurate account stats: This release introduces code to pull up-to-date counts of statuses, followers, and following from remote instances and show these stats via the API. So now in your client of choice, you should see an accurate count of the number of statuses and followers/following of a given account, no more "0 followers, 0 following, 0 statuses".
  • HTTP header permissions settings: The settings panel now has a section that allows admins to set regular expressions to deny requests depending on HTTP headers.
    Documentation here: docs.gotosocial.org/en/latest/…
  • Filters v2 implementation: We've now implemented the v2 API for filters, which means you can create more complex filters to hide keywords or statuses, and more clients should be able to create filters on GoToSocial.
  • Send test email: Admins can now use the settings panel to send a test email, to check if their SMTP (email) configuration is valid.
  • Profile API: Clients that use the profile API to delete avatar + header images should now work, since we've now implemented this part of the API.
  • Search operators: We've added a first search operator to GoToSocial, so when you're searching for statuses, you can add from:@[username]@[domain] to your search term, to search only within statuses created by the given account (while still respecting the search limitations we already had in place).
    Documentation here: docs.gotosocial.org/en/latest/…
  • Email change: Users can now change their email address in the settings panel without admin intervention.
    Documentation here: docs.gotosocial.org/en/latest/…
  • Memory usage optimizations: GoToSocial now uses memory more conservatively than before; you should only need about 150-200MiB of memory to run GtS with a full cache, and it will spike less.

Release v0.16.0 Snappy Sloth · superseriousbusiness/gotosocial

Hello internet! Roll up roll up and see ye all version 0.16.0 of GoToSocial, codename SNAPPY SLOTH. Release highlights Sign up / registration: In this release, you can open your instance to new re...
GitHub
#GoToSocial #pooping

Hello hello good morning, here's the second release candidate for #GoToSocial v0.16.0!

github.com/superseriousbusines…

We fixed a bug that was preventing brand new instances from federating properly, and a bug where two accounts could refer to each other as moved_to targets.

Get it while it's fresh! 🍞 ☕️


Release v0.16.0-rc2 · superseriousbusiness/gotosocial

Hiya! Second RC for 0.16.0! No db migrations or config file changes between v0.16.0-rc1 and this version, so upgrading is as simple as updating your docker container or stopping GtS, untarring the ...
GitHub
#GoToSocial

i made a CLI tool for moving data in and out of GtS and Mastodon instances using the API: github.com/VyrCossont/slurp

it can handle CSV data in Mastodon export format for blocks, bookmarks, follows, and lists. there is no Mastodon CSV format for filters so i made one up. (note that you need to be running GtS 0.15 for filter support.)

it doesn't handle posts or media yet; i have ideas about extending the GtS API to allow backdating posts and suppressing push federation, but probably won't get to that for a while.

#GtS #GotoSocial


GitHub - VyrCossont/slurp: tool for exporting data from and importing data to Fediverse instances

tool for exporting data from and importing data to Fediverse instances - VyrCossont/slurp
GitHub
#GoToSocial #gts

Hello everyone!

We've just made the first release candidate for version 0.16.0 of #GoToSocial, aka Snappy Sloth.

github.com/superseriousbusines…

For adventurous instance admins, please read the release + migration notes very carefully when updating to this release, paying particular attention to the database migrations section.

Here are the release highlights:

  • Sign up / registration: In this release, you can open your instance to new registrations (aka sign-ups) via the new signup page at https://[your-instance.tld]/signup. No more manually creating new users via the CLI :)
    Documentation here: docs.gotosocial.org/en/latest/…
  • Accounts overview for moderators: To support the new sign-up feature, and help instance admins to moderate, we made a new section in the settings panel where admins + moderators can get an overview of accounts, and filter by instance, status, and more. You'll find this new accounts view in the settings panel.
  • Totally reworked message delivery system and worker queues: We've completely reworked the way GoToSocial sends out messages to your followers and performs worker-related tasks; this should drastically increase the speed that outgoing messages are delivered, especially for users with lots of followers. It also paves the way for future work in terms of persisting worker and message queues over restarts.
  • Account mutes: The account mute API endpoints are now implemented, meaning you can put (timed) mutes of accounts in place, to hide statuses from specific accounts from your home timeline, and/or hide notifications from muted accounts.
  • Accurate account stats: This release introduces code to pull up-to-date counts of statuses, followers, and following from remote instances and show these stats via the API. So now in your client of choice, you should see an accurate count of the number of statuses and followers/following of a given account, no more "0 followers, 0 following, 0 statuses".
  • HTTP header permissions settings: The settings panel now has a section that allows admins to set regular expressions to deny requests depending on HTTP headers.
    Documentation here: docs.gotosocial.org/en/latest/…
  • Filters v2 implementation: We've now implemented the v2 API for filters, which means you can create more complex filters to hide keywords or statuses, and more clients should be able to create filters on GoToSocial.
  • Send test email: Admins can now use the settings panel to send a test email, to check if their SMTP (email) configuration is valid.
  • Profile API: Clients that use the profile API to delete avatar + header images should now work, since we've now implemented this part of the API.
  • Search operators: We've added a first search operator to GoToSocial, so when you're searching for statuses, you can add from:@[username]@[domain] to your search term, to search only within statuses created by the given account (while still respecting the search limitations we already had in place).
    Documentation here: docs.gotosocial.org/en/latest/…
  • Email change: Users can now change their email address in the settings panel without admin intervention.
    Documentation here: docs.gotosocial.org/en/latest/…
  • Memory usage optimizations: GoToSocial now uses memory more conservatively than before; you should only need about 150-200MiB of memory to run GtS with a full cache, and it will spike less.

Release v0.16.0-rc1 Snappy Sloth · superseriousbusiness/gotosocial

Hello you nerds, dorks, and dweebs ❤️ This here is the first release candidate for version 0.16.0 of GoToSocial, codename SNAPPY SLOTH. Release highlights Sign up / registration: In this release, ...
GitHub
#GoToSocial

⇧