#gotosocial

I can confirm that #Tuba is an excellent #Fediverse client for Linux and BSD users on #snac2. It's also great for Mastodon, #GoToSocial, etc.

#Mitra can query outgoing follow requests now, same endpoint as #gotosocial

#gotosocial was really nice and easy to setup - but does not have a web client built-in. I would prefer that.

can anyone recommend a lightweight #ActivityPub server+client, will probably be max 5-10 users?

snac2 looks good, but i think i might have to fiddle with the stylesheet quite a bit..

is misskey good?

halp

#askfedi #smallweb #selfhost #yunohost

Recap for an activitypub instance.

Good morning Fedi friends!

Monday mornings mean: my weekly ritual of manually backing up my #YunoHost installation (my VPS does automatic daily backups of the whole VPS, but I say: better safe than sorry).

This latest backup is pretty big, because of my increased use of #NextCloud. So in reverse order, from biggest to smallest we have:

1) #GoToSocial : 5.8 GB
2) #PeerTube : 4.3 GB
3) #NextCloud: 3.7 GB
4) #Pixelfed : 1.6 GB
5) #LinkStack : 92 MB
6) #Fail2Ban : 362kb

Happy #selfhosting everyone! And in case you missed it, my self-hosting guide for newbies via YunoHost is available here: https://blog.elenarossini.com/a-newbies-guide-to-self-hosting-with-yunohost/ (with 4 articles so far).

Have a great week everyone!

#MySoCalledSudoLife

Dear fellow or potential fellow gotosocial instance admins,
I've come up with a novel way to set up a #gotosocial server behind a reverse proxy, which avoids the use of making new firewalling rules - both on a VPS, and creating port forwarding on one's home router. This method is ideal for minimizing the cost of running one's own #ActivityPub/#Mastodon server, in a way that leverages inexpensive fast storage on the backend (say, on a #RaspberryPi 5, 2GB of RAM, with an NVMe). As many valiant and praiseworthy Mastodon server admins might attest to, renting cloud VPS' can cost a lot, especially when storing many tens or hundreds of GB of user data.

My method avoids the need of forwarding ports 443 and 80 into one's home LAN, using DNAT (on the VPS) and port forwarding (on one's home router). In a nutshell, it's a novel use of #Wireguard, in conjunction with #nginx on the frontend, and gotosocial on the backend. This can save the cost of renting a dedicated VPS, to get the exclusive use of ports 443 and 80, in conjunction with static IPv4 and IPv6 addresses. My method optimizes on reliability and cheapness, but it's not the most secure - decryption and re-encryption happens on the VPS, before the data travels down the Wireguard tunnel. This exposes the data to any underlying hypervisor at one's hosting company. So full disclosure there.

I've run my method by the helpful gotosocial furries in their #Matrix Help chatroom (and I'm grateful for their help to debug subtle warts the method had), and got their blessing, at least to the technical soundness of the method.

I have a testing instance of gotosocial 0.21.0 set up with this new method: https://g.toque.im

I'm the user @owl on that instance, should you wish to befriend me there.

I'll make a longer blog post on this in the days to come, and post it in a reply to this post. (I also cross-posted this on another account of mine, please forgive the duplicate: @gtsadmin )

#DevOps #Linux #infosec #SelfHosting #DataSovereignty #OpenSource

#gotosocial fue el primer sistema para el #fediverso que probé instalar pars texto-plano y fue un fracaso rotundo porque no me federaba pero he visto últimamente que se está usando más y parece que ya funciona.

#snac por otra parte fue más simple y rápido, no tiene una gran estética pero siempre me ha funcionado bien

Hello everyone, version 0.21.0 of #GoToSocial, aka Sacrilegious Sloth, has emerged from the release candidate process, ready to serve your nasty blasphemous posting needs 🥰

https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.21.0

Please read the migration notes carefully for instructions on how to upgrade to this version! There are database migrations and config file changes to be aware of.

Here are the release highlights:

• Domain 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-indexable
• Show 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-profile
• Better 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!

Getting a #gotosocial instance properly running is NOT easy! Split domains is giving me a splitting headache!

Can any of you nice #mastodon #selfhosting folks please check if you can at least see the option to follow for @amplisci@gts.social.typescholar.com ?

Attention #GoToSocial people: I have been testing @mastoblaster - an iOS Fediverse client - and it's working SO WELL! It's even grouping GtS notifications... something that Ivory doesn't do.

More info here:

🔗​: https://mastoblaster.app

Congratulations @stefano for your brilliant work on it!

#snac #MastoBlaster