Piero Bosio Social Web Site Personale

Hello nerds!We've just created the first release candidate version of #GoToSocial v0.21.0 Sacrilegious Sloth!https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.21.0-rc1Adventurous admins can try updating to this release candidate, and let us know if there's any new and interesting bugs to be found.We're really proud of this one, the sloth is starting to feel really useable and good!Please read the migration notes carefully for instructions on how to upgrade to this version. Bear in mind there are a few big-ish database migrations in this one, which may take somewhere between a minute or 20+ minutes to run (depending on your hardware). Be patient, backup your database first, and don't interrupt the migrations.Release highlightsDomain Limits: You can now create domain limits in the admin section of the settings panel, in order to do things like limit + mute all accounts on a domain (except ones you follow), add content warnings to posts from limited domains, mark media as sensitive (or don't download it at all).Documented here: https://docs.gotosocial.org/en/latest/admin/domain_limits/Indexable support: You can now mark your account as "indexable" by full-text search, in the settings panel. This will federate your preference to other servers, so that servers with full-text search functionality can include your posts in search results.Documented here: https://docs.gotosocial.org/en/latest/user_guide/settings/#mark-accounts-posts-as-full-text-indexableShow reblogs on the web view of your profile (opt-in): A new setting in the settings panel allows you to opt-in to showing posts that you've boosted/reblogged on the web view of your profile. The default setting retains existing behavior (don't show boosts on the web view).Documented here: https://docs.gotosocial.org/en/latest/user_guide/settings/#include-boosts-on-the-web-view-of-your-profileBetter caching behavior for timelines. The number of database calls when browsing local + public timelines and lists should be significantly reduced.Store + show reason for undownloaded media: When media fails to be downloaded from a remote instance, the reason why will be shown next to the post.Include canQuote property on outgoing posts: Currently, this is always set to author-only, but it paves the way (and signals intent) for GtS to implement quote toots at some point.Much improved OpenGraph previews: Whitespace is now preserved in OpenGraph previews, and media + formatting was rejigged, so linking to GoToSocial posts should result in much better OpenGraph-generated preview cards.Expand/collapse all spoilers button on web view of threads: when viewing threads in the web view, you can now expand/collapse all spoilers at the click of a button.S3 Object Info Caching: you can now configure cache.s3-object-info in order to mitigate expensive S3 info calls when doing nightly media cleanup.Preserve significant whitespaces in incoming + outgoing posts: previously we were squashing a lot of whitespace together, which meant that, for example, indentation could get lost on posts federated into a GoToSocial instance. This is now fixed, so you can post poetry and whatnot without worrying about it looking like hot crap.Millions of fucking bugfixes: we squashed a lot of them!

So out of interest how long do you both keep your posts for ? At the moment mine are indefinate.CC: @passthejoe@snac.bsd.cafe

Just an #AskFedi session. I currently installed my GoToSocial instance on VPS and now I'm conflicted about how to organize the project better. GoToSocial is needed to interact with Fediverse users, as the other platforms miss some activities. ⁃ WriteFreely: very good, minimal to write, but it has no space for search or comments. It's OK just for the stories.⁃ WordPress: it has federation through plugin, comments appearing on the site, but not yet usable as a fediverse actor for common interaction, with an ordinary client. Icecubes, Mona, Phanpy, Enafore, Tweesecake, Elk, etc. And "enable mastodon apps" is still buggy.⁃ As I have contents both in Italian and English, I currently have to choose: do I federate the English and Italian WordPress sites where real world and long-form fictions are published, and have just an unified project's instance on GoToSocial where I personally talk (me and my other co-worker) both in Italian and English? I honestly am very conflicted. #activitypub #gotosocial #WordPress

@matzElk ha un problema che secondo me è abbastanza grosso: se lo vuoi installare te lo fanno scaricare direttamente come pacchetto per docker. Ora, ok, vabbeh, uno si arrangia credo, scarica i sorgenti e compila, ma per principio preferisco venga specificata una scelta, fosse anche due righe che dicono "teh, se non vuoi docker questi sono i sorgenti, git clone, make, make install"@perry @steko

@Sascha thank you Sascha. I used to be stuff like that on my other VPS - which had a Ghost-CLI installation. With YunoHost I don't dare go in the backend to touch anything, lest I disrupt something. I have too many important apps in that installation. I'm not incurring in any extra costs... it's just that a social networking app caches media, avatars and emojis of everyone I follow. I found an old backup from December 2024 when I was only following one account and it was 256 MB! Pruning the list of people I follow - it overlaps with my Mastodon account - may be the way to go 😅​

Looking for testers for a new Mastodon TUI.tooi is a re-implementation of the TUI included with toot, using a more modern framework which is easier to work with. It supports most features `toot tui` does, and some new ones too.tooi is set to replace `toot tui` which has proven to be troublesome to support and extend.https://codeberg.org/ihabunek/tooi#toot #mastodon #pleroma #gotosocial #tui #terminal

@aerion 🥰🙌🥳 thanks for sharing. Self-hosting is really the best@_elena @snikket_im

@BastilleBSD that's strange as gotosocial is usually quite stable (I've tested it inside a FreeBSD jail).snac2 is working properly with enafore, semaphore, ecc. More apps/frontend will be supported when as soon as the incompatibilities will be detected (for example, I fixed a couple of problems and now it's compatible with Moshidon)

@Linkshaender Thank you! You too!

@silhouette @stereo @gotosocial congrats as well! 🥳​

Hello everyone!As we do every year, we're taking some time off for the holidays.This year, the #GoToSocial maintainer holiday period will last from December 19th up to and including January 4th, so we'll be back in action on January 5th.What this means:We will make our matrix chat (general, help, and code channels) read-only.We will disable our issue tracker on Codeberg so that we don't have to worry about tracking + triaging issues.1We may do little bits of work if we feel like it, but we won't be reviewing any pull requests from others.2We will be absolutely chilling our tits off and doing fun stuff with friends, family, lovers, and whatnot.We're looking forward to recharging our batteries over the holidays, and coming back in January ready to kick some ass!Thanks for reading, and happy holidays to you <3 ​ 🏳️‍⚧️ ​ 🏳️‍🌈Unfortunately, Codeberg doesn't let you just make issues read only, so we'll have to disable / hide the issues tracker entirely during this time, unlike previous years when we were on Github. ↩︎Codeberg also doesn't (yet!) let you disable pull requests for everyone but maintainers. ↩︎

@stereo thank you Ralf! I wish I (a) spoke German (b) could have attended one of your workshops. Thank you for all your FOSS and digital literacy advocacy 🙏​ and of course for your help and encouragement with my experimentations ☺️​

@_elena @teapot_ben Matomo is really powerful, yet easy to use, I have been using it since it was called Piwik which was a long time ago. Definitely recommended

@JuleLe when I ran into a similar problem I just upgraded to a higher tier. But with Hetzner apparently you can easily do it... discussion here: https://www.reddit.com/r/hetzner/comments/1125618/hetzner_cloud_add_more_storage/

neat, #GoToSocial got featured in Codeberg's latest newsletter good sloth

e vabbeh, aggiorniamo!CC: @gotosocial@superseriousbusiness.org

One final annoyance with my @gotosocial migration!I implemented a split-domain setup, as wonderfully documented by @gotosocial here: docs.gotosocial.org/en/latest/Note that #Mastodon also supports it, and documents it similarly here: docs.joinmastodon.org/admin/coIn both Mastodon and #GoToSocial, I notice that web clients FAIL to login with the account domain.From what I see on the web server, the account domain receives exactly ONE request:"POST /api/v1/apps HTTP/2.0" 404 146 "-" "Tusky/31.1 Android/15 OkHttp/5.1.0"(This is Tusky, but Mastodon's app and others behave the same)I tried to 301 / 307 redirect that endpoint (against @gotosocial's recommendation), but that fails in the same way (except I see the different matching code on the web server).As a side effect, apps show my username as: at evilham at fedi.unchat.cat, instead of @evilham, which is what I actually wanted.What to do? >,<

@luca how do you solve the DNS and port problem?

@klu9 installing Sharkey on my TLD bricked the whole installation (because I’m such an airhead sometimes) so I’m nuking that VPS and trying again this morning 🫠

@giacomo @informapirata @beachcomber @alephoto85 Snac2 is great. The only thing that got me back at hosting a full mastodon instance was because I wanted to use a mastodon mobile app fully. So it depend how you intend to use it :)But like I just said; a mastodon app. Snac2 is not Mastodon. It has, howerver, a "compatibility" mastodon API. It was just not enough for me personally.But beside that; Snac2 is really a game changer. Stable, reliable and low on memory/cpu usage.