does anyone know of any good fedi front end clients that are tailored towards long form blog posts? i want to turn todiy into a multi media platform, and not just microblogging, but i don't wanna have to run a separate server/subdomain for every format! I think i like the idea of using #GoToSocial as a backend because it seems pretty flexible! i dont want my users to need a bazillion accounts lol. Im looking at #writefreely , and it would be awesome to use its front end somehow. #fediadmin
El servidor #Activitypub que estic programant ja té operatives les funcionalitats bàsiques:
webfinger ✅
nodeinfo ✅
activitat "Follow" (seguir usuari) ✅
activitat "Undo" (deixar de seguir) ✅
signar activitats "Accept" ✅
La app oficial ja troba el servidor i ja mostra el missatge "Mastodon vol utilitzar aquest servidor per a iniciar sessió" (encara no he afegit l'algorisme d'inici de sessió 😅)
Quan ja funcioni l'inici de sessió faré els algorismes de les línies de temps. #appy
I can finally respond to polls here again. After migrating to GoToSocial I had lost that possibility, but with the new release candidate that changes. This is another significant improvement. I really enjoy my self-hosted GoToSocial instance. :blobcatsip:
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 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/
we're trying to narrow down a (bizarre, kind of funny) #GoToSocial bug where a boosted status can appear in timelines to be authored by the person who boosted it -- so essentially boosting a status can sometimes "steal" that status
it's a bugger to reproduce, so if you see it, and you have any useful info to share about it (either in logs, or in the Network tab of your browser when looking at the status in a client) please do share
#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.
The alpha version of @gotosocial now has support for allowlists.
Allowlists automatically prevent federation with all other servers, except those that the admin has added to their allowlist. (Traditional blocklists work the other way round, allowing all federation unless a server is blocked.)
Allowlists bring more safety but also reduce reach, and that's why it's up to each admin to decide whether to use them.
📌 If there's someone wondering where I am at, currently I am more active at @hnb which on my own #GoToSocial solo server. I thought I would keep posting here too but it did not turn that way...for now.
:blobfox3c:
Working on some better language tag support for #GoToSocial, including being able to set preferred server language(s). It won't do much yet but it will be important down the line.
Looks like my #gotosocial is way faster now that it's running on new storage (and RAID1 instead of single drive now). But: somehow not all servers seem to have noticed that my instance is back 🙃
@ajroach42 Sounds solid to me. #GoToSocial also looks cool too though I haven't looked too hard at it. If I was looking at a server for just me or my immediate family I would probably seriously consider that over anything in the masto or pleroma/akkoma realm.
Seems like a good choice to focus on a small number of distinct options for fedi hosting.
Placeholders for unknown media attachment types are merged into #GoToSocial and will be in 0.13.0 :)
This means that if someone posts a media attachment of a type your instance doesn't recognize or can't process (funky video types, pdfs, image types we don't support yet), or if there's a network issue fetching a piece of media, it will no longer just be thrown away.
Instead you'll be served a link to the remote URL for that piece of media, so you can open it in directly in your (mobile) browser.
The next time you refresh that status (2hr cooldown), your instance will try again to fetch the piece of media, and automagically update the status if it succeeds.
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.
This week I boosted posts from #GoToSocial and #Akkoma instances and followed someone on a #Funkwhale instance all from my #Mastodon instance, as if they were all Mastodon posts and accounts.