@gotosocial@superseriousbusiness.org
@gotosocial@superseriousbusiness.org avatar

gotosocial

@gotosocial@superseriousbusiness.org

The official account for GoToSocial news, updates, release announcements, and so on!

GoToSocial is an open-source, ActivityPub compatible, federated social media server. It's easy to install, lightweight, and runs quite well on small servers 🦥

GoToSocial is still alpha software. Your support is appreciated as we fix bugs, add features, and move towards beta ❤️

This is not a support account! Support questions addressed to this account will go unanswered. For support please see the links!

This profile is from a federated server and may be incomplete. Browse more on the original instance.

gotosocial, to random EN
@gotosocial@superseriousbusiness.org avatar

Hi everyone! From the 8th of May up to + including the 22nd of May we'll be on holiday here at GoToSocial :)

This means we'll be making the Github repository read-only for issues for the duration, and making the Matrix help/general channels read-only too.

We have a tradition of doing this a couple times a year to chill and refresh ourselves, step away from the computers and do more stuff IRL without feeling the pressure to check our notifs all the time, and just generally recuperate, and it's worked out pretty great so far, so we'll keep doing it!

If you need to reach us about anything urgent between the 8th and the 22nd we will still check our email address inbox (admin@gotosocial.org) occasionally.

After the break, we'll start gearing up for the 0.16.0 release, which should be a good one ^_^

Thanks for reading! <3

gotosocial, to movies EN
@gotosocial@superseriousbusiness.org avatar

Hello sportsfans!

The proper release of v0.15.0 Shagadelic Sloth has emerged blinking into the sun, fresh from the release candidate process :) One of our funkiest releases ever, since it contains some beautiful new themes you can try out (see screenshots).

You can get the release here:

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

As always, please read the migration notes carefully! This release contains important database migrations that you should not interrupt!

Highlights of this release:

Soft themed GtS profile. Gentle pinks and blues with rounded edges.
Midnight trip themed GtS profile. Bold chunky magenta borders and neon green highlights.
Dark blurple themed GtS profile. Deep purples and with yellow highlight.

gotosocial, to movies EN
@gotosocial@superseriousbusiness.org avatar

Hey nerds! 🌸

First spring time release of #GoToSocial, here's the first release candidate for version 0.15.0 Shagadelic Sloth!

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.15.0-rc1

For adventurous admins updating to this release candidate, please read the migration notes carefully, especially regarding database migrations :)

Release highlights

Midnight trip: chunky purple and neon-green theme with magenta ombre.
Soft: a light pink, blue, and white theme.
Sunset: yellow / orange / aubergine theme with a sunset ombre.

gotosocial, to random EN
@gotosocial@superseriousbusiness.org avatar

#GoToSocial bugfix release v0.14.1!

👢
🐛

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

There was a bug in 0.14.0 which was causing SQLite-backed instances to sometimes become unresponsive, with lots of errors in the logs containing interrupted(9) (see https://github.com/superseriousbusiness/gotosocial/issues/2728).

We poked around and this looks like an issue in our SQLite dependency, so we stepped down to the most recent stable version, and also added some code to prevent the problem from rendering an instance unresponsive.

No db migrations or config file changes between v0.14.0 and this version, so upgrading is as simple as updating your docker container or stopping GtS, untarring the release, and starting GtS again.

For instructions to update to this release from versions < v0.14.0, see the v0.14.0 release notes, but replace v0.14.0 with v0.14.1 throughout.

Thanks!

gotosocial, to random EN
@gotosocial@superseriousbusiness.org avatar

Hi everyone!

We've just released v0.14.0 of #GoToSocial! Say hello to the Spoiled Sloth :gtspat:

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

We're really proud of this release! It fixes a lot of longstanding annoying bugs, and adds some very neat features tooooo

Thanks to everyone who helped us with code and trying out release candidates and filing issues, and a big thank you to all our financial supporters who help us out via opencollective and liberapay :)

When upgrading to this version from a previous release, please note that there are CSS and HTML updates, config file changes, and several database migrations which may take a while to run! So please read the migration notes carefully :)


Release highlights:

  • Account aliasing. You can now set the alsoKnownAs field on your account via the settings panel, to indicate other accounts you own. This doesn't do much now, but it's the first step towards the Move implementation for account migration coming in v0.15.0. We originally wanted to include Move in this release but it needs more testing so we pushed it back. Hang in there :)
  • Much better thread sorting. Conversation threads on both the web view and client API use a new sorting mechanism which makes them way more readable. No longer will replies in a thread be scattered all over the place.
  • Better HTTP signature support. We fixed a longstanding issue with including vs not including query parameters in signed GET requests. We now try (and accept) both methods of constructing signatures. Which leads to...
  • Improved thread fetching. You'll see far fewer "orphaned" statuses in your timeline now, and you'll see more replies on statuses from other instances.
  • Syntax highlighting for code blocks on the web UI. When you include a code block in your markdown now, and correctly indicate the language the code is written in, it will be syntax highlighted when rendered on your profile in the web UI. This requires javascript, but it's a progressive enhancement feature. Visitors to your profile with javascript turned off will just see the code block without syntax highlighting :)
  • Improved "about this instance" page, with a link to the page in the nav bar. Previously the "about this instance" page was more or less hidden. We've now surfaced it better, so you can write all your terms and conditions and instance description stuff there. Relatedly....
  • Parse instance descriptions and terms and conditions as markdown. Previously it was very difficult to properly edit these fields, because you had to read + write HTML to do so. Now they're parsed as markdown. This means you can more easily include things like blockquotes, lists, etc.
  • Big refactor of HTML templates + CSS. We did a serious rework of HTML templates to fix indentation. Previously if you did "view source" on a GoToSocial profile page, you'd see a mess of sloppily-indented HTML. With this refactor, the HTML is now nicely indented and much more readable. We also did an accessibility pass and tested our HTML with various screen readers to try to make the web view a bit less annoying to navigate.
  • First pass at a basic spam filtering system. In light of spam waves happening on the fediverse recently we took a crack at implementing a filter to drop messages identified as spam. This is still in the experimental stage, but it's included in this release so you can try it out already. See the docs for details.
floppy, to random
@floppy@fosstodon.org avatar

Hey @gotosocial, thank you for all the work you put into making great software!

I'm running a small instance for friends. I'm moderating, but did not have much time to update to the latest releases recently. When updating, can I skip releases, e.g. from 0.11.x to 0.14.x?

I am aware of other likely required changes such as adapting the config file, as stated in the release notes.

gotosocial,
@gotosocial@superseriousbusiness.org avatar

@floppy yes, you can

gotosocial, to random EN
@gotosocial@superseriousbusiness.org avatar

Hi everyone! We just made the second release candidate (rc2) for #GoToSocial v0.14.0. Here it is!

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.14.0-rc2

What happened to the first release candidate, you say? Well, it didn't work properly 🤦 But this one does.

If you're the type of badass admin who uses release candidates, please give it a shot :) If you find any bugs particular to this release candidate, let us know on our issues page so we can fix them before 0.14.0 proper.

As always, please read the migration notes carefully!

Highlights of this release (candidate):

  • Account aliasing. You can now set the alsoKnownAs field on your account via the settings panel, to indicate other accounts you own. This doesn't do much now, but it's the first step towards the Move implementation for account migration coming in v0.15.0. We originally wanted to include Move in this release but it needs more testing so we pushed it back. Hang in there :)
  • Much better thread sorting. Conversation threads on both the web view and client API use a new sorting mechanism which makes them way more readable. No longer will replies in a thread be scattered all over the place.
  • Better HTTP signature support. We fixed a longstanding issue with including vs not including query parameters in signed GET requests. We now try (and accept) both methods of constructing signatures. Which leads to...
  • Improved thread fetching. You'll see far fewer "orphaned" statuses in your timeline now, and you'll see more replies on statuses from other instances.
  • Syntax highlighting for code blocks on the web UI. When you include a code block in your markdown now, and correctly indicate the language the code is written in, it will be syntax highlighted when rendered on your profile in the web UI. This requires javascript to be enabled in a visitor's web browser, but it's a progressive enhancement feature. Visitors to your profile with javascript turned off will just see the code block without syntax highlighting :)
  • Improved "about this instance" page, with a link to the page in the nav bar. Previously the "about this instance" page was more or less hidden. We've now surfaced it better, so you can write all your terms and conditions and instance description stuff there. Relatedly....
  • Parse instance descriptions and terms and conditions as markdown. Previously it was very difficult to properly edit these fields, because you had to read + write HTML to do so. Now they're parsed as markdown. This means you can more easily include things like blockquotes, lists, etc.
  • Big refactor of HTML templates + CSS. We did a serious rework of HTML templates to fix indentation. Previously if you did "view source" on a GoToSocial profile page, you'd see a mess of sloppily-indented HTML. With this refactor, the HTML is now nicely indented and much more readable. We also did an accessibility pass and tested our HTML with various screen readers to try to make the web view a bit less annoying to navigate.
  • First pass at a basic spam filtering system. In light of spam waves happening on the fediverse recently we took a crack at implementing a filter to drop messages identified as spam. This is still in the experimental stage, but it's included in this release so you can try it out already. See the docs for details.

Thanks for reading!

gotosocial,
@gotosocial@superseriousbusiness.org avatar

@zlatko direct to this should work :) just be prepared for a bit of a wait while the db migrations run

gotosocial,
@gotosocial@superseriousbusiness.org avatar

@esoteric_programmer this is not a support account, please direct questions like this to our matrix space or github repo (links in bio)

gotosocial,
@gotosocial@superseriousbusiness.org avatar

Hello hello, here's the third release candidate for #GoToSocial v0.14.0!

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.14.0-rc3

Just a few bug fixes and dependency bumps over the previous release candidate.

If all looks good, this RC will become the final 0.14.0 release in a couple days time :)

Thanks for reading!

gotosocial, to random EN
@gotosocial@superseriousbusiness.org avatar

Hi everyone! We just made another security + bugfix release for #GoToSocial

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

If you're running on v0.13.2 or below, you should update to this release as soon as you have the time. There are no database migrations or frontend file changes, so this should be fairly easy!

Similar to the v0.13.2 release, this one closes a couple gaps with regard to ensuring that remote accounts and statuses can't be imitated.

It also fixes a couple different bugs with regard to your instance trying to dereference accounts who've blocked you, or whose instances have blocked you, leading to less weird-looking behavior from the user's side :)

Oh, and as a nice side effect of the above changes, federation with Bookwyrm should work a bit better now too! 📖 🪱

If you're running on a main snapshot build, you should update to the latest code on main by either refreshing the Docker snapshot tag, or taking the latest binary snapshot bundle.

Now with that out of the way we can get on with working on features for 0.14.0 :P

Thanks for reading! Have a good Thursday! :under_construction:

gotosocial, to random EN
@gotosocial@superseriousbusiness.org avatar

Hello hello! We just made a bugfix/security release of GoToSocial, v0.13.2.

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

Background

After Mastodon announced some vulnerabilities last week we looked through equivalent parts of our own code to make sure GtS isn't vulnerable in the same way.

Good news

We didn't find anything that would allow anyone to take over an account, or to post statuses or do updates as someone else: we check Create and Update activities carefully.

Bad news

We did find some areas where remote accounts could, with persistence and custom software, make a nuisance of themselves by pretending to be other accounts and sending fakes of a subset of activities such as Likes, Blocks, Follows, Announces (boosts), and Undo's of those things.

The above is not really easy to do, and we don't have any evidence that anyone's actually done it, but hey, now it's fixed just in case.

So, if you're running v0.13.1 or below, we recommend updating to v0.13.2 using the link above. The release doesn't contain any changes to the config file or templates or anything, so it should be a quick and easy update.

If you're running on main/snapshot: we recommend updating your snapshot to the latest code on main, which includes the fix. You can get the latest snapshot binary build from here or, for docker, update your docker image to the latest snapshot tag. Depending on how far back in commits you were before this release, there may be config file changes or other things, but likely nothing breaking.

As always, thanks for reading, and enjoy your week!

gotosocial, to random EN
@gotosocial@superseriousbusiness.org avatar

We're well on the way to #GoToSocial 0.14.0 release candidate 1!

Based on the sheer amount of fixes and improvements included, 0.14.0 will probably be the biggest release we've done so far :gtspat:

It will also (probably, unless something goes wrong) be the first GoToSocial release to include support for the Move activity, which will let you migrate an existing account to or from a GoToSocial instance, while keeping your followers and following relationships intact :) We waited a long time to write this functionality because we wanted to make sure GoToSocial was in a decent state before people start migrating accounts to it.

So, very exciting! If all goes well, expect more news on the first release candidate in a couple weeks (we're still fixing some bugs, as always).

gotosocial, to journalism EN
@gotosocial@superseriousbusiness.org avatar

Hello nerds!

We recently updated our user manual to add a section on media uploads, including image descriptions and which bits of metadata (exif tags) are and aren't excised from media uploads.

https://docs.gotosocial.org/en/latest/user_guide/posts/#media-attachments

We were reminded recently that while GoToSocial strips metadata reliably from image types, we don't yet strip metadata from videos. That means that if you have "location data" or "geotagging" enabled in the camera app of your device when you record a video, and you upload that video without re-encoding it or removing metadata tags from it in some other way, location data may be encoded into the video file, which presents a privacy issue.

Unlike corpo social media, many fedi implementations (to the best of our knowledge) remove sensitive metadata when they compress/reencode images/videos, or at least give you the option to configure your server to do so.

As such, the fact that GtS doesn't yet strip metadata from videos specifically will probably be a "gotcha" for some users coming from other fedi softwares. A warning about this has now been added to the docs, but we're putting the warning out here too so people are aware of the issue.

So, please be careful when uploading videos! If you haven't done so already, we recommend going to your device's camera app and turning off "location data" so that video clips do not have your coordinates added to them.

We will be adding this issue to the list of things to do before we leave alpha and enter beta, and we'll announce it here when we implement a fix.

Thanks for reading :)

gotosocial, to random
@gotosocial@superseriousbusiness.org avatar

At some point in this first quarter of 2024 we plan to mark the Alpha development phase of GoToSocial as completed, and "officially" enter the Beta phase. This will happen prettymuch whenever we get account migration working properly via the Move activity, and also implement a basic sign up flow to augment the current manual account creation process done via the CLI tool.

Every software development process is different, but in our case, Beta will mean that we consider most of the very basic features to be complete, the software is reasonably stable, and we can then start adding other cool stuff like better moderation tools, better oauth tooling, status edits, and that sort of thing (see our roadmap for more details).

It's been a long and interesting alpha period. tobi started GtS as more or less a hobby project during a period of day-job burnout at the start of 2021. They got GtS federating fairly quickly, started seeing the potential in it for more than just a hobby project, and then other folks like kim, daenney, f0x, and maloki jumped in to work on the project too, as well as a whole bunch of semi-regular and drive-by contributors. tobi kept working on the project during their absence from work, and then kept going after they left their job and started taking unemployment benefits, and then continued (spending their last savings) after the benefits dried up.

In late 2022 when Twitter shat the bed for the umpteenth time, we saw interest in GoToSocial skyrocket, which was both scary and exciting. Suddenly way more people were running the software and finding bugs and reporting issues, which was overwhelming and stressful but also very, very helpful for the stability of the software.

In 2023, we managed to get funding from NLnet to continue working on the project, which couldn't come soon enough since tobi was, by the start of 2023, completely broke. Thanks to NLnet, tobi could now work on GoToSocial full time without worrying excessively about money, which was a huge relief.

Now in 2024, kim is also working full time on GoToSocial, having also got an NLnet grant, which gives us a lot more confidence in terms of the sustainability of working on the software. It's going to be a good year for GtS :) Big thank you to NLnet for believing in us.

Throughout this whole period, people donated over and over to our liberapay and opencollective, which helped us to pay for our CI/CD development machine, and gave us a buffer for unexpected bills and shocks. Thank you so much!

Over the course of alpha we discovered a whole bunch of weird bugs, leading to many headaches and late nights toiling over fmt.Printf statements and writing tests. We made the software way more resilient and flexible in terms of how it federates, poked through the code of other AP implementations to discover and work around edge cases, and generally worked very, very hard on stability and compatibility. We're not 100% there yet in terms of which other softwares GtS can properly communicate with, but given how divergent AP implementations are from each other, and how many softwares do wacky undocumented things, we think it's going pretty damn well.

And we found time to add features too! In 2023 we merged support for:

  • hashtags
  • polls
  • status language tags
  • allowlist federation
  • account notes
  • timeline markers
  • lists
  • partial search
  • profile fields
  • request tracing
  • prometheus metrics
  • pinned posts
  • (most) mp4 videos
  • bookmarks

So, there you go! A little potted, messy history of GoToSocial so far. Probably missing a bunch of important things that happened but memory is fickle.

Thanks for your ongoing support and kindness, and here's to a fun upcoming beta development period in a few months :gtspat: :under_construction:

gotosocial, to random EN
@gotosocial@superseriousbusiness.org avatar

hello nerds, it's #GoToSocial bugfix release time!

0.13.1 Spiderier Sloth fixes a couple small issues with poll vote counts and poll expiry, and an issue where domain blocks were sometimes not being properly enforced when deeper- and higher-level domain blocks were used in combination (eg., when combining blocks for say example.org, bad.example.org, also-bad.example.org).

There are no database migrations or config file changes on this one, so upgrading from 0.13.0 should be very simple :)

You can get the release from here: https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.13.1

Enjoy!

gotosocial, to random
@gotosocial@superseriousbusiness.org avatar

Our holiday has begun :) As foretold, our channels are now read only up to (and including) 2nd of Jan, so we'll be back around 3rd of Jan. Reminder that this isn't a support account, so tagging this account for support will get you nowhere (and we'll be using it less while we're on holiday anyway). For urgently pressing matters, email admin@gotosocial.org. Thank you all for a neato 2023, have a great couple weeks, and see you in the new year! :gtspat: ❤️

gotosocial, to random
@gotosocial@superseriousbusiness.org avatar

Now that #GoToSocial 0.13.0 is out, we are preparing to take a break :)

If you've been following us for a while, you'll know that every year over the holidays we like to make our github repository and matrix channels read only for a while. This lets us step back from support work for a few weeks, and focus on things other than GoToSocial (seeing friends and family, playing video games, reading, cuddling our pets), in order to recharge our mental and emotional batteries and come into the new year feeling fresh and excited again.

This year, we'll take our holiday from (and including) the 19th of December, up to (and including) the 2nd of January. During this time:

  • the three GtS matrix channels will be read only
  • the github repo will be read only for non-members of the org (though you may still see us pushing commits and whatnot)
  • we will be less active on this account

So, if you spot any issues with v0.13.0, please file them before the 19th, or save them until after the 2nd.

Thanks for reading! ❤️

gotosocial, to KindActions EN
@gotosocial@superseriousbusiness.org avatar

Hi everyone!

We've just released a new version of #GoToSocial, v0.13.0 aka Spider Sloth!

You can get the release from here: https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.13.0

As usual, please read the migration notes carefully when upgrading to this version.

Thanks! Enjoy!


Highlights of this release:

  • Create, view, and vote in polls. It's been a while in the making but GoToSocial now has support for polls, aka Question activity types. You can create, view, and vote in polls using your client of choice.
  • Show unsupported media placeholders in incoming posts, where media could not be downloaded (temporarily or otherwise). No more dropped media on posts! You'll instead now get a link to the media on the originating instance, that you can click through in your (mobile) browser.
  • Mute threads that you're being overwhelmed by. Notifications for replies, likes, and boosts in that thread will no longer be generated.
  • Media cleanup scheduling. Previously media scheduling took place every night at 12am. With the new media scheduling settings in the config, you can customize the schedule to run it at different times and frequencies. https://docs.gotosocial.org/en/latest/admin/media_caching/#cleanup
  • Support for setting instance language . You can use the new instance-languages setting to indicate one or more primary languages for your instance. https://docs.gotosocial.org/en/latest/configuration/instance/
  • Support for language tags on posts. Language of posts is now correctly federated in and out of your instance. The language of posts is also shown on the web view of statuses and threads.
  • Gather and expose prometheus format metrics. You can now expose a /metrics endpoint to allow a Prometheus instance to scrape metrics about Go runtime memory usage, http request and database metrics, and more. https://docs.gotosocial.org/en/latest/advanced/metrics/
gotosocial, to random EN
@gotosocial@superseriousbusiness.org avatar

those boosts from some of our core developers should help clear up our position on Threads, if it didn't already need to be said.

gotosocial, to random EN
@gotosocial@superseriousbusiness.org avatar

Hiya! It's a gloomy day so here's a little ray of sunshine:

We just tagged + pushed the second release candidate for 0.13.0 of GoToSocial!

This contains mostly fixes for pesky bugs from the first release candidate. You can get rc2 here:

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.13.0-rc2

Note that on SQLite, when you start up your instance an analyze will run when you switch to this version. The analyze might take a good few minutes to run, depending on how large your SQLite database is, and how performant your system is. Please be patient and don't interrupt it, it's optimizing your database :)

As usual, if you find any bugs specific to this release candidate, please open them on our issue tracker.

Thanks for reading, and enjoy the release candidate!

#GoToSocial #Slothware

gotosocial, to KindActions EN
@gotosocial@superseriousbusiness.org avatar

Happy Friday everyone! Hope you're staying warm!

To celebrate the weekend, here's the first release candidate (rc1) for #GoToSocial 0.13.0 Spider Sloth!

https://github.com/superseriousbusiness/gotosocial/releases/tag/v0.13.0-rc1

As always, please read the migration notes carefully when updating. If you find any bugs in the release candidate, kindly let us know on Github!

Release highlights below the line.


  • Create, view, and vote in polls. It's been a while in the making but GoToSocial now has support for polls, aka Question activity types. You can create, view, and vote in polls using your client of choice.
  • Show unsupported media placeholders in incoming posts, where media could not be downloaded (temporarily or otherwise). No more dropped media on posts! You'll instead now get a link to the media on the originating instance, that you can click through in your (mobile) browser.
  • Mute threads that you're being overwhelmed by. Notifications for replies, likes, and boosts in that thread will no longer be generated.
  • Media cleanup scheduling. Previously media scheduling took place every night at 12am. With the new media scheduling settings in the config, you can customize the schedule to run it at different times and frequencies. https://docs.gotosocial.org/en/latest/admin/media_caching/#cleanup
  • Support for setting instance languages . You can use the new instance-languages setting to indicate one or more primary languages for your instance. https://docs.gotosocial.org/en/latest/configuration/instance/
  • Support for language tags on posts. Language of posts is now correctly federated in and out of your instance. The language of posts is also shown on the web view of statuses and threads.
  • Gather and expose prometheus format metrics. You can now expose a /metrics endpoint to allow a Prometheus instance to scrape metrics about Go runtime memory usage, http request and database metrics, and more. https://docs.gotosocial.org/en/latest/advanced/metrics/
gotosocial, to random EN
@gotosocial@superseriousbusiness.org avatar

#GoToSocial 0.13.0 Spider Sloth is coming along well. We've got a few little bugs to fix before making a first release candidate, and then we can let our little spidery child out into the world. It's quite an exciting release, so we'd like to get as many nuts and bolts tightened as possible so that it goes smoothly.

In particular, we've found a cheeky little bug in our png decoding, which sometimes causes pngs to fail to be downloaded from remote instances. We'll spend a bit more time poking and prodding this one, because it actually gets around the media placeholder logic we added.

More soon!

gotosocial, to random
@gotosocial@superseriousbusiness.org avatar

Next GtS release (0.13.0 Spider Sloth) will be a doozy:

  • Polls!
  • Support language tags of incoming/outgoing posts.
  • Media placeholders for unknown/errored media types.
  • Custom cleanup scheduling.
  • First pass at prometheus metrics implementation.
  • Thread muting / unmuting.

Couple weeks probably, we're still fixing some bugs 🐛 ⚠️

#GoToSocial

gotosocial, to random
@gotosocial@superseriousbusiness.org avatar

Hiya! We made a small security bugfix release for #GoToSocial, version 0.12.2 Spaghettiest Sloth

You can get the release from here:

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

Notes from the release:

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.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • Leos
  • kavyap
  • cisconetworking
  • thenastyranch
  • magazineikmin
  • hgfsjryuu7
  • DreamBathrooms
  • InstantRegret
  • Youngstown
  • slotface
  • PowerRangers
  • Durango
  • everett
  • rosin
  • anitta
  • vwfavf
  • modclub
  • ethstaker
  • khanakhh
  • tacticalgear
  • ngwrru68w68
  • osvaldo12
  • mdbf
  • tester
  • cubers
  • normalnudes
  • GTA5RPClips
  • provamag3
  • All magazines