#Tag
Two more #GoToSocial PRs today:
follows domain limit policies, such as RejectAll, RejectNonMutual, ManualApproval etc.ContentWarning property when serializing posts from a limited domain via the APIIt's gonna be nice having domain limit stuff in place fully! :gtspat:
#NLnet published their policy on so-called "ai" in projects they sponsor, and while it's a fucking bummer to see them say "We are not against GenAI", they are at least requiring grantees to disclose use of so-called "ai", including requiring a list of prompts used for so-called "substantive" use thereof:
https://nlnet.nl/foundation/policies/generativeAI/
As always, #GoToSocial in particular explicitly forbids would-be contributors to the code or docs from using "ai" tools in contributions. Our considered stance remains "fuck 'AI' all the way to hell".
#NLnet published their policy on so-called "ai" in projects they sponsor, and while it's a fucking bummer to see them say "We are not against GenAI", they are at least requiring grantees to disclose use of so-called "ai", including requiring a list of prompts used for so-called "substantive" use thereof:
https://nlnet.nl/foundation/policies/generativeAI/
As always, #GoToSocial in particular explicitly forbids would-be contributors to the code or docs from using "ai" tools in contributions. Our considered stance remains "fuck 'AI' all the way to hell".
Good morning Fedi friends!
This week I will publish a first post in my mini series for total newbies about how to self-host with #YunoHost.
The very first article will simply cover the basics of what is needed... then part 2 will be the step-by-step installation and connecting a domain + creating a subdomain... and then part 3 will cover installing an app (NextCloud) and setting up a backup system.
I'm hoping to get all this done before Christmas, in time for my one year anniversary of self-hosting with YunoHost (thank you again @ilja for setting all this in motion last year).
As I type this, I'm currently backing up my YunoHost and these days my backup files are about 13GB in size, broken down as follows (in descending order):
Wishing you all a great day & week!
wrote a cheeky /api/v1/admin/media_purge endpoint that can be called from the settings panel:
https://codeberg.org/superseriousbusiness/gotosocial/pulls/4613
useful to run after creating a domain limit with reject set as the media policy
#selfhosting con #yunohost pare che #gotosocial sia il processo che consuma più RAM (245 MB circa), seguito da #rsshub e poi mysql/mariadb che fondamentalmente fa girare wordpress.
Ora la domanda è quanto di questo consumo sia legato a vari bot e scrapers AI. Temo che siano prevalenti, il mio singolo utente è veramente una goccia nel mare e segue pochissimi account. Ma come si fa per arginare il problema?
After an embarrassingly long time, I figured out how to reset a password on a GoToSocial instance. You have to run the reset command, **AND THEN RESTART THE SERVER**.
It was that last part that tripped me up. I stopped reading after the password reset command. Oops.
From inside the docker container:
`./gotosocial admin account password --username USERNAME --password PASSWORD --config-path config.yaml`
The exit out of the container and run
`docker restart gotosocial`
Have you considered making your own #GoToSocial server?
GoToSocial is a new Fediverse platform which is lighter than Mastodon and has more user safety features. It's compatible with Mastodon apps so there are already lots of ways to use it.
You don't need to be techy to set up a GTS server, there are managed hosting providers at https://fedihost.co/hosting/gotosocial and https://communick.com/gotosocial
If you ARE techy, there are manual installation instructions at https://docs.gotosocial.org
Good morning Fedi friends!
This week I will publish a first post in my mini series for total newbies about how to self-host with #YunoHost.
The very first article will simply cover the basics of what is needed... then part 2 will be the step-by-step installation and connecting a domain + creating a subdomain... and then part 3 will cover installing an app (NextCloud) and setting up a backup system.
I'm hoping to get all this done before Christmas, in time for my one year anniversary of self-hosting with YunoHost (thank you again @ilja for setting all this in motion last year).
As I type this, I'm currently backing up my YunoHost and these days my backup files are about 13GB in size, broken down as follows (in descending order):
Wishing you all a great day & week!
#selfhosting con #yunohost pare che #gotosocial sia il processo che consuma più RAM (245 MB circa), seguito da #rsshub e poi mysql/mariadb che fondamentalmente fa girare wordpress.
Ora la domanda è quanto di questo consumo sia legato a vari bot e scrapers AI. Temo che siano prevalenti, il mio singolo utente è veramente una goccia nel mare e segue pochissimi account. Ma come si fa per arginare il problema?
Have you considered making your own #GoToSocial server?
GoToSocial is a new Fediverse platform which is lighter than Mastodon and has more user safety features. It's compatible with Mastodon apps so there are already lots of ways to use it.
You don't need to be techy to set up a GTS server, there are managed hosting providers at https://fedihost.co/hosting/gotosocial and https://communick.com/gotosocial
If you ARE techy, there are manual installation instructions at https://docs.gotosocial.org
I host my own Phanpy but there's a feature in dev (automatically populate alt-text if it's embedded in images, yessss!!!) I really want. So, I finally setup a build container for @phanpy and a small script to extract out the static folder so I can continue serving it out via Caddy. I wrote a quick post about it, I'm sure there are better and more idiomatic ways of doing this, so advice is welcome.
@hikingdude thank you Franz and hello @CryogenicNighthawk 👋
The account where I chronicle my self-hosting adventures is: @elena ( #GoToSocial, self-hosted via the superb #YunoHost)
Alright here's what it looks like creating a domain limit in the settings panel.
It's very similar to the process of creating a domain allow or block, you just enter the domain you wanna limit, pick the ways in which you wanna limit it, add a comment etc if you want, and submit it.
The options for limits are (currently, though subject to some change):
content warning:
media from the limited domain:
follows from the limited domain targeting an account on this domain:
statuses from the limited domain created by non-followed accounts:
non-followed accounts on the limited domain:
the statuses and accounts policies are designed in such a way that if you follow an account on a limited domain with one or more of these limits applied, you more or less aren't affected cuz you'll be able to see stuff that the account posts as normal; the fact that you follow them is taken as evidence that you wanna see their posts (I mean... why else would you follow them). However if you don't follow them you can make it so your instance functionally ignores their existence, from your perspective at least
the other policies allow you to follow accounts on instances that, for example, post lots of tits, ass, and genitalia (hurray!) but don't use content warnings or mark stuff as sensitive (boo!); you can just have your instance apply content warnings and mark stuff as sensitive for you
this shooooooould more or less allow you to federate with instances that are a bit shit overall, but which contain one or two cool people, without getting a massive headache and wanting to throw your laptop into the hole
docs to follow when the feature is actually on main and everything is working
I host my own Phanpy but there's a feature in dev (automatically populate alt-text if it's embedded in images, yessss!!!) I really want. So, I finally setup a build container for @phanpy and a small script to extract out the static folder so I can continue serving it out via Caddy. I wrote a quick post about it, I'm sure there are better and more idiomatic ways of doing this, so advice is welcome.
#gotosocial listed in the #codeberg community spotlight
https://blog.codeberg.org/letter-from-codeberg-onwards-and-upwards.html
A space for Bonfire maintainers and contributors to communicate
