Hello everyone! We've just made the first release candidate for version 0.17.0 of GoToSocial Adventurous admins who want to try the new features and help us spotting bugs can get the release from below:
⚠️ This release contains several database migrations which will run the first time you start up this new version. Be sure not to interrupt this migration process. This will take anywhere between a few seconds and an hour or even more (on slower hardware / big databases). Please be patient! Back up your database file before updating! We had to rejig the entire statuses table to introduce interaction policies (see below). ⚠️
Release highlights:
Interaction policies: This release gives you the ability to set interaction policies on your statuses using the settings panel. Interaction policies let you determine who can reply to, like, or boost your statuses. You can accept or reject interactions as you wish; accepted replies will be added to your replies collection, and unwanted replies will be dropped. This feature is still a work-in-progress as we will almost certainly have some kinks to work out in terms of implementation etc, but we wanted to get it into people's hands as quickly as possible. User docs here: docs.gotosocial.org/en/latest/… Federation docs here: docs.gotosocial.org/en/latest/…
Much wider range of support for different media types: In this release we've embedded a webassembly build of ffmpeg into the GoToSocial binary, so that users can post many different types of media than previously, including mp3, flac, and other audio types, and many more video types. Admins: you don't need to have ffmpeg installed on your server for this to work.
Audio player: to complement the new media types, we adapted our current video player to also play audio, so people visiting your profile can play MP3s and FLACs. Album art is supported when embedded in the audio file!
Header/avatar alt text: You can now set alt-text for your avatar + header images, so that screenreader users visiting your profile can read a description of your beautiful face.
Better threading model for statuses: On the web view of a thread, conversations are now indented at different levels, to make it easier to see who's replying to whom.
Prefers-reduced-motion is now supported, so that folks with animations turned off in their operating system or browser aren't confronted with lots of animation when they open your profile.
Conversations view: You can now view a list of your direct message conversations, making it much easier to keep track of who you're talking to.
Import/export csv files: It's now possible to import Mastodon-compatible CSV files for accounts you follow and accounts you block, making it much easier to migrate across instances. Export of these files is supported too.
Exclusive lists: You can now mark lists as "exclusive", which means that posts from accounts in an exclusive list will show up only in that list and not in your home timeline.
Show/hide posts on your profile: Previously only Public posts were shown on your web profile. This is still the default, but you can now choose to show unlisted posts on your web profile too (the Mastodon default), or to show no posts at all.
Lots of new themes: solarized, brutalist, ecks pee, and more.
Store worker queue on restart: when you stop the instance, pending tasks are stored into the database, and loaded again when you start up the instance, so that no tasks get lost between restarts.
Thanks for helping us find bugs everyone! You've found some good ones so far and all the bug reports have been very specific and helpful, which is great! ^_^ We're working away on squashing them in preparation for v0.17.0-rc2.
One thing we've noticed so far is that some folks have struggled with the database migrations from 0.16.0 or below to 0.17.0-rc1. This is a reminder to please please please back up your database before doing this update, and also please please be patient and let the migrations run.
It's a huge set of migrations because we had to change big chunks of the statuses table for the new features, and for storage-saving reasons. If your database is small and new you probably won't even notice the migrations but if it's a large-ish database of a few GB and you're running on a low-powered machine they might take bloody ages.
If the migrations fail, running them manually is a huge pain in the arse, so the best bet is always to just restore your pre-update backup and try again; this is why we added the "back up your database" steps to the update instructions.
If you're running in very resource-constrained environments (ie., 512MiB ram machines, machines where you're pushing up against your disk size limit), you may want to free up a bit of overhead before doing the migrations, as we've seen (on SQLite) that they can be a bit demanding.
Anyway! As stated above, most people haven't had problems, but better safe than sorry!
We fixed some bugs! Quite a few bugs actually. And we snuck a new theme in there, and updated the way we distribute Accepts of interactions.
If updating to this release candidate from 0.17.0-rc1, there's just one little database migration to run, which should be quite fast.
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 rc2.
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.
We've found one bug in the RC so far to do with replies to statuses from remote accounts not being put into "pending approval" state. We'll make a fix tomorrow or so :) Apart from that, hearing positive reviews of this release candidate so far, so we're getting there!
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.
So far we've seen that there may be some memory issues for FreeBSD users running their instances with SQLite. The issue is that memory usage is far higher than it should be on those specific setups. We're currently investigating why this might be happening.
If you are one of the unlucky folks running into this issue, could you please try using this alternative build of the GoToSocial release candidate that we just uploaded, which uses a different SQLite driver?
Calling all coders! Developers! Programmers! Hackers! Whatever you want to be called 😊 Join the LibreOffice Development Workshop at our upcoming conference, and learn more about Git, Gerrit, C++, building large codebases and more: blog.documentfoundation.org/bl…
Darf ein evangelischer Theologe hinter die #Allmacht Gottes ein Fragezeichen setzen? Beginnt nicht das Apostolische #Glaubensbekenntnis mit der #Omnipotenz Gottes? Ich habe in der Bibel und bei #Bonhoeffer nachgelesen. Mein Blogbeitrag dieses Sonntags.
My wife Kirsten @MoonCat and I decided to give potential podcasting a go. I know, 'Not another one?' But we hope this might be a bit of light entertainment for you. Consider this a pilot to see how things go.
In this first episode we discuss a somewhat annoying Tiktok trend I heard about in a video, the point of hugging and our love of the 'Cautionary Tales' podcast from Tim Harford.
@menelion I've only literally just made it now, so I don't have an RSS feed or even sure how to set one up, but I've just put it up on my server, for those who don't want to go near youtube.
I have nothing against YouTube, it's just a matter of catching up quickly. If you need tips for setting up a podcast, ask here, I or someone else will definitely help.
@TheCube @jakobrosin Yeah, either install something like WordPress, or, I guess the geekiest way, to write a script that would generate the feed for you.
In der Schweiz zahlen Milliardäre einen höheren Steuersatz als in Deutschland und Menschen aus der Mittelschicht dafür einen viel niedrigeren. Eine Vermögensteuer ist machbar. Das Bürgerbegehren „Tax the rich“ sammelt dafür gerade EU-weit Unterschriften. #TaxTheRich gew.de/aktuelles/detailseite/w…
У создателя известной онлайн-библиотеки «Флибуста» обнаружили большую злокачественную опухоль мозга, и прогноз, очевидно, весьма неутешительный. flibusta.is/comment/3561561 Грёбаный рак! #Флибуста
C2S server for matrix.org accounts is blocked in Russia using deep packet inspection (DPI). That means people can no longer access their accounts without resorting to censorship circumvention technology.
The website and S2S federation server are still reachable from Russia.
How effective are bug bounties in securing critical, open source infrastructure? On 30 Sep 2024 in Berlin, following a keynote by Sabine Grützmacher (MdB), Dr. Ryan Ellis will present his research and dive into FOSS, security, and the public interest with an expert panel. Details & agenda for the evening event: sovereigntechfund.de/programs/…
All apps must comply with the authorities. Are you suggesting we should go dark and use apps that are deliberately not complying with authorities?
The problem with Telegram is not they are sharing these infos with the authorities. All apps that have access to these already do. It is that they can access and give access to so much more than this.
it's not so much what app I'd use (don't use Telegram anyway), but more a case of trying to persuade others to move... and that's difficult enough, especially Messenger and WhatsApp users!
Me parece una postura interesante, y desde leugo estoy de acuerdo en la importancia de socializar los medios de comunicación y las redes sociales. Lo que veo menos claro es esa tendencia de separa las redes sociales corporativas de otras hegemonías en los medios de comunicación de masas. No hicieron falta rdes sociales para colar el timo de la conspiración del 11M al país, solo el poder de la prensa, radio, y tele de toda la vida.
Creo que hay una cierta lucha sectorial interburguesa entre los propietarios de editoriales, televisiones, y otros medios de comunicación contra los propietarios de centros de datos, cables submarinos de fibra, y demás; y en esa lucha soy bastante neutral, porque no me creo que el periódico sea bueno y democrático y TikTok malo y antidemocrático en contraste.
Regular reminder that if you do this with your webapps, you're a part of the problem, and any attempts to reason with me on that will be met with laughter and image macros.
Ok, I should be sleeping right now, but what's happening is SO FUCKING CRAZY.
Long story short: WPEngine is suing Matt Mullenweg, Automattic and the WordPress foundation for slandering them. In return, Matt is suing them for trademark violation.
But, BUT, WPEngine has fired their first shot. And what a shot it is, friends:
Stunningly, Automattic’s CEO Matthew Mullenweg threatened that if WP Engine did not agree to pay Automattic – his for-profit entity – a very large sum of money before his September 20th keynote address at the WordCamp US Convention, he was going to embark on a self-described “scorched earth nuclear approach” toward WP Engine within the WordPress community and beyond. When his outrageous financial demands were not met, Mr. Mullenweg carried out his threats by making repeated false claims disparaging WP Engine to its employees, its customers, and the world. Mr. Mullenweg has carried out this wrongful campaign against WP Engine in multiple outlets, including via his keynote address, across several public platforms like X,YouTube, and even on the Wordpress.org site, and through the WordPress Admin panel for all WordPress users, including directly targeting WP Engine customers in their own private WordPress instances used to run their online businesses
During calls on September 17th and 19th, for instance, Automattic CFO Mark Davies told a WP Engine board member that Automattic would “go to war” if WP Engine did not agree to pay its competitor Automattic a significant percentage of its gross revenues – tens of millions of dollars in fact – on an ongoing basis. Mr. Davies suggested the payment ostensibly would be for a “license” to use certain trademarks like WordPress, even though WP Engine needs no such license. WP Engine’s uses of those marks to describe its services – as all companies in this space do – are fair uses under settled trademark law and consistent with WordPress’ own guidelines. Automattic’s CFO insisted that WP Engine provide its response to this demand immediately and later, on the day of the keynote, followed up with an email reiterating a claimed need for WP Engine to concede to the demands “before Matt makes his WCUS keynote at 3:45 p.m. PDT today.”
In parallel and throughout September 19 and 20, Mr. Mullenweg embarked on a series of harassing text messages and calls to WP Engine’s board member and also its CEO, threatening that if WP Engine did not agree to pay up prior to the start of Mr. Mullenweg’s livestreamed keynote address at 3:45pm on September 20, he would go “nuclear” on WP Engine, including by smearing its name, disparaging its directors and corporate officers, and banning WP Engine from WordPress community events.
They... they have text message captures. In the pdf. Matt Mullenweg was trying to extort them ... by text messages. They seem to have the entire thing in the writting.
In the final minutes leading up to his keynote address, Mr. Mullenweg sent one last missive: a photo of the WordCamp audience waiting to hear his speech, with the message that he could shift gears and turn his talk into “just a Q&A” if WP Engine agreed to pay up
They finish requesting Automattic to "preserve, and not destroy, any and all documents or information in their possession, custody, or control that may be relevant to any dispute between WP Engine and Automattic". They are going to war, big time.
All this crap is just because they refuse to pay his protection money. And the guy has been stupid enough to put everything in writting.
35% of #bisexual men in a relationship *with another man* have never told that partner about their bisexuality. And only the minority of us are very or fairly open about our #bisexuality to our male partners. That's from ILGA Europe. The norm is for us bi #men to be quiet about our bisexuality, even in same-gender relationships. #Gay men, you can think about that one during #BiVisibilityDay.
If China can do these evil things with their proprietary cars, then so can U.S. and Japanese cars.
Make the rule fair: ban proprietary cars.
(But it's not about being fair, it's about the U.S. wanting to preserve the ability to use domestic cars for spying, while preventing other countries from having that ability.)
Adventurous admins who want to try the new features and help us spotting bugs can get the release from below:
GoToSocial
in reply to GoToSocial • • •GoToSocial
in reply to GoToSocial • • •Thanks for helping us find bugs everyone! You've found some good ones so far and all the bug reports have been very specific and helpful, which is great! ^_^ We're working away on squashing them in preparation for v0.17.0-rc2.
One thing we've noticed so far is that some folks have struggled with the database migrations from 0.16.0 or below to 0.17.0-rc1. This is a reminder to please please please back up your database before doing this update, and also please please be patient and let the migrations run.
It's a huge set of migrations because we had to change big chunks of the statuses table for the new features, and for storage-saving reasons. If your database is small and new you probably won't even notice the migrations but if it's a large-ish database of a few GB and you're running on a low-powered machine they might take bloody ages.
If the migrations fail, running them manually is a huge pain in the arse, so the best bet is always to just restore your pre-update backup and try again; this is why we added the "back up your database" steps to the update instructions.
If you're running in very resource-constrained environments (ie., 512MiB ram machines, machines where you're pushing up against your disk size limit), you may want to free up a bit of overhead before doing the migrations, as we've seen (on SQLite) that they can be a bit demanding.
Anyway! As stated above, most people haven't had problems, but better safe than sorry!
Thanks for reading ❤
GoToSocial
in reply to GoToSocial • • •Hello again! We've just made the second release candidate for v0.17.0!
github.com/superseriousbusines…
We fixed some bugs! Quite a few bugs actually. And we snuck a new theme in there, and updated the way we distribute Accepts of interactions.
If updating to this release candidate from 0.17.0-rc1, there's just one little database migration to run, which should be quite fast.
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
rc1withrc2.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 for reading!
GoToSocial
in reply to GoToSocial • • •GoToSocial
in reply to GoToSocial • • •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
in reply to GoToSocial • • •So far we've seen that there may be some memory issues for FreeBSD users running their instances with SQLite. The issue is that memory usage is far higher than it should be on those specific setups. We're currently investigating why this might be happening.
If you are one of the unlucky folks running into this issue, could you please try using this alternative build of the GoToSocial release candidate that we just uploaded, which uses a different SQLite driver?
github.com/superseriousbusines…
If the issue is resolved with that build, please let us know :)