#Tag · bonfire.cafe

tobi is writing bugs :terminal_cursor:

@dumpsterqueer@gts.superseriousbusiness.org · 3 hours ago

alright here's how the form and the cheatsheets for domain limits ended up looking on the frontend

https://codeberg.org/superseriousbusiness/gotosocial/pulls/4567

#GoToSocial #GoPissGirlSocial #GoGoGadgetArms

Bottom half of the domain limit edit page, showing account policy, statuses policy, and follows policy options.

Screenshot of the domain limit detail view for an existing limit. There's text boxes for public and private comment and content warning. The "media policy" section is also visible and reads:

You can apply a media policy in order to change whether and how your instance processes media attachments from the limited domain.

Cheatsheet:

No limit
Media will be processed as normal.
Mark sensitive
Media will be processed as normal.
However, all post attachments from the limited domain will be marked sensitive.
Reject
No media from the limited domain will be downloaded, processed, or stored.
This includes emoji, avatars, headers, and media attachments.
Posts will contain a link to view attached media on the remote instance. — Screenshot of the domain limit detail view for an existing limit. There's text boxes for public and private comment and content warning. The "media policy" section is also visible and reads: You can apply a media policy in order to change whether and how your instance processes media attachments from the limited domain. Cheatsheet: No limit Media will be processed as normal. Mark sensitive Media will be processed as normal. However, all post attachments from the limited domain will be marked sensitive. Reject No media from the limited domain will be downloaded, processed, or stored. This includes emoji, avatars, headers, and media attachments. Posts will contain a link to view attached media on the remote instance.

Screenshot of the domain limits search + overview page in the settings panel, with the following text:

Domain limits can be used to modify how your instance handles posts, follow requests, media, and accounts from remote domains. This allows you to "fine-tune" federation with a domain without having to resort to putting a full domain block in place to cut off federation entirely. For example, you can use a domain limit to mute all accounts on a given domain except for ones people on your instance follow, and/or to mark all media from a given domain as "sensitive", etc. When you create a domain limit, it extends to all subdomains as well, so limiting 'example.com' also limits 'social.example.com'. — Screenshot of the domain limits search + overview page in the settings panel, with the following text: Domain limits can be used to modify how your instance handles posts, follow requests, media, and accounts from remote domains. This allows you to "fine-tune" federation with a domain without having to resort to putting a full domain block in place to cut off federation entirely. For example, you can use a domain limit to mute all accounts on a given domain except for ones people on your instance follow, and/or to mark all media from a given domain as "sensitive", etc. When you create a domain limit, it extends to all subdomains as well, so limiting 'example.com' also limits 'social.example.com'.

GoToSocial

@gotosocial@gts.superseriousbusiness.org · 12 hours ago

Next GtS release (0.13.0 Spider Sloth) will be a doozy:

Polls!
Support language tags of incoming/outgoing posts.
Media placeholders for unknown/errored media types.
Custom cleanup scheduling.
First pass at prometheus metrics implementation.
Thread muting / unmuting.

Couple weeks probably, we're still fixing some bugs 🐛 ⚠️

#GoToSocial

fedicat boosted

FediHost

@fedihost@mstdn.social · 2 days ago

#GoToSocial will be updated to the latest version by tomorrow which will restore compatibility with #Mastodon.

We've been working on it all week, a few changes in the code have required us to make alterations to our systems and run a lot of tests and simulations.

Sorry for the delays.

tobi is writing bugs :terminal_cursor:

@dumpsterqueer@gts.superseriousbusiness.org · yesterday

Making a sort of cheatsheet thingy so you don't have to remember what these policies actually do, or go look at the docs in a separate page

#GoToSocial #MoreLikeGoPooSocialAmIRight

The work-in-progress domain limit page, showing Media Policy and Follows Policy options. There's a little dropdown you can click that explains what each option in the policy does. For example, for media policy the explainer says:

No limit
Media will be processed as normal.
Mark sensitive
Media will be processed as normal.
However, all post attachments from the limited domain will be marked sensitive.
Reject
No media from the limited domain will be downloaded, processed, or stored.
This includes emoji, avatars, headers, and media attachments.
Posts will contain a link to view attached media on the remote instance. — The work-in-progress domain limit page, showing Media Policy and Follows Policy options. There's a little dropdown you can click that explains what each option in the policy does. For example, for media policy the explainer says: No limit Media will be processed as normal. Mark sensitive Media will be processed as normal. However, all post attachments from the limited domain will be marked sensitive. Reject No media from the limited domain will be downloaded, processed, or stored. This includes emoji, avatars, headers, and media attachments. Posts will contain a link to view attached media on the remote instance.

FediHost

@fedihost@mstdn.social · 2 days ago

#GoToSocial will be updated to the latest version by tomorrow which will restore compatibility with #Mastodon.

We've been working on it all week, a few changes in the code have required us to make alterations to our systems and run a lot of tests and simulations.

Sorry for the delays.

tobi is writing bugs :terminal_cursor: and 2 others boosted

kimothy siddon

@kim@k.iim.gay · 4 days ago

psssst latest #gotosocial minor release is out, and it has some nice improvements for S3 storage users 👀

https://gts.superseriousbusiness.org/@gotosocial/statuses/01KA96WV1S08T6QQKBGGRH2ZZQ

in particular:
https://codeberg.org/superseriousbusiness/gotosocial/pulls/4545
https://codeberg.org/superseriousbusiness/gotosocial/pulls/4546

also some nice little performance improvements for everyone:
https://codeberg.org/superseriousbusiness/gotosocial/commit/d1812357b3882409ac5b6cb987881547c8370619
https://codeberg.org/superseriousbusiness/gotosocial/commit/14bf8e62f81d7eac637f2097a88b4c3c32a8a7b5
https://codeberg.org/superseriousbusiness/gotosocial/commit/ddf887d95c1cef95746f9881dc4180d983e7a351

Codeberg.org

[performance] handle emoji refreshes asynchronously when fetched as part of account|status dereferences (#4486) · d1812357b3

# Description Updates our dereferencer emoji handling to work asynchronously when going through the route of account or status dereferencing. closes https://codeberg.org/superseriousbusiness/gotosocial/issues/4485 ## Checklist - [x] I/we have read the [GoToSocial contribution guidelines](htt...

Codeberg.org

[performance] add optional S3 object info caching

# Description This adds an optional S3 object info cache to the S3 storage driver backend (see [here](https://codeberg.org/gruf/go-storage/releases/tag/v0.4.0)) to reduce S3 calls largely during media cleanup operations, but it should also help in other situations cutting back on S3 calls when f...

GoToSocial and 3 others boosted

GoToSocial

@gotosocial@gts.superseriousbusiness.org · 4 days ago

Hello everyone!

Here's version 0.20.2 of #GoToSocial; it's another bugfix release!

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

If you're updating to this version from v0.20.0 or v0.20.1, it's a very easy update with no db migrations.

If you're updating to this version from a version before v0.20.0, please follow the update instructions from v0.20.0, but replace 0.20.0 with 0.20.2 throughout. Be aware that the update to 0.20.x contains some potentially very long migrations. Please do read the notes carefully!

Release highlights:

Roll back to using name property instead of summary for alt text (for now anyway), due to compatibility issues with *oma, *key, and Iceshrimp.
Stub authorize_interaction to avoid surprising 404 when trying to do a remote interaction.
Fix issue that was causing emojis not to download properly.
Add optional build tags for reduced binary size.
Fix some swagger docs issues.
Various other fixes + performance tweaks.
Dependency bumps.

Thanks for reading! Have a good week!

Codeberg.org

v0.20.0 Sinister Sloth 😈 - superseriousbusiness/gotosocial

Here's version 0.20.0 of GoToSocial, **Sinister Sloth**. It's been a long summer of gently poking and prodding at the sloth's tummy and sides to make xem giggle. Now that autumn is here and the weather is getting crisp, xe's finally ready to lumber out the door and say hello. In a sinister man...

GoToSocial

@gotosocial@gts.superseriousbusiness.org · 4 days ago

Hello everyone!

Here's version 0.20.2 of #GoToSocial; it's another bugfix release!

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

If you're updating to this version from v0.20.0 or v0.20.1, it's a very easy update with no db migrations.

Release highlights:

Roll back to using name property instead of summary for alt text (for now anyway), due to compatibility issues with *oma, *key, and Iceshrimp.
Stub authorize_interaction to avoid surprising 404 when trying to do a remote interaction.
Fix issue that was causing emojis not to download properly.
Add optional build tags for reduced binary size.
Fix some swagger docs issues.
Various other fixes + performance tweaks.
Dependency bumps.

Thanks for reading! Have a good week!

Codeberg.org

v0.20.0 Sinister Sloth 😈 - superseriousbusiness/gotosocial

kimothy siddon

@kim@k.iim.gay · 4 days ago

psssst latest #gotosocial minor release is out, and it has some nice improvements for S3 storage users 👀

https://gts.superseriousbusiness.org/@gotosocial/statuses/01KA96WV1S08T6QQKBGGRH2ZZQ

in particular:
https://codeberg.org/superseriousbusiness/gotosocial/pulls/4545
https://codeberg.org/superseriousbusiness/gotosocial/pulls/4546

Codeberg.org

[performance] handle emoji refreshes asynchronously when fetched as part of account|status dereferences (#4486) · d1812357b3

Codeberg.org

[performance] add optional S3 object info caching

tobi is writing bugs :terminal_cursor: boosted

Adam - K3CAN

@me@social.k3can.us · 4 days ago

Alright, I think I've got it mostly working.

#gotosocial running on a #Google WiFi router from 2016.

https://blog.k3can.us/tags/googlewifi/

If it remains stable, I'll share the address of the instance itself for anyone who wants to check it out.

Do I win the award for most wasted weekend?

Googlewifi - K3CAN's Blog

Adam - K3CAN

@me@social.k3can.us · 4 days ago

Alright, I think I've got it mostly working.

#gotosocial running on a #Google WiFi router from 2016.

https://blog.k3can.us/tags/googlewifi/

If it remains stable, I'll share the address of the instance itself for anyone who wants to check it out.

Do I win the award for most wasted weekend?

Googlewifi - K3CAN's Blog

Adam - K3CAN

@me@social.k3can.us · 4 days ago

Alright, I think I've got it mostly working.

#gotosocial running on a #Google WiFi router from 2016.

https://blog.k3can.us/tags/googlewifi/

If it remains stable, I'll share the address of the instance itself for anyone who wants to check it out.

Do I win the award for most wasted weekend?

Googlewifi - K3CAN's Blog

⁂ Kaleb

@kaleb@fedi.haugenh.us · 4 days ago

Looking for some help with interaction issues between NGINX, HTMX, and GoToSocial.

The issue

My GET request from my website HaugenHus | Now Test

 hx-get="https://fedi.haugenh.us/@kaleb/feed.rss"
hx-headers='{"Accept": "application/feed+json"}'

…is returning two basic CORS errors:

[Error] Request header field HX-Request is not allowed by Access-Control-Allow-Headers.
[Error] XMLHttpRequest cannot load https://fedi.haugenh.us/@kaleb/feed.rss due to access control checks.

…that I can’t figure out how to resolve.

Things I’ve tried

I ’ve added

add_header 'Access-Control-Allow-Origin' 'https://fedi.haugenh.us';
add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
add_header 'Access-Control-Allow-Headers' 'Content-Type, Authorization, Accept, HX-Request';

to my nginx.conf (actually I’ve imported it from another .conf and verified that the config is being included with nginx -T), but it has no impact on the errors.

I have confirmed that the page loads successfully including the remote JSON when I set my browser to ignore CORS.

Additionally, I am able to successfully load the remote feed.rss when I use the hx-request='{"noHeaders": true}’, but doing so returns XML rather than the desired JSON due the JSON Feed implementation in GoToSocial RSS

#GTS #GoToSocial #nginx #CORS #JSONFeeds #HTMX

tobi is writing bugs :terminal_cursor: and 1 other boosted

tobi is writing bugs :terminal_cursor:

@dumpsterqueer@gts.superseriousbusiness.org · 5 days ago

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:

if you want, you can automatically prepend a content warning to posts from the limited domain

media from the limited domain:

no limit (default)
always mark as sensitive
don't download or process at all, just link to it instead (kinda how we do already for media that GtS couldn't download for whatever reason)

follows from the limited domain targeting an account on this domain:

no limit (default)
always require manual approval, even if the follow targets an unlocked account
automatically reject unless the follow (request) is a "follow back", ie., the target account already follows or follow requests the account on the limited domain
automatically reject all

statuses from the limited domain created by non-followed accounts:

no limit (default)
apply a "warn" filter to all statuses
apply a "hide" filter to all statuses

non-followed accounts on the limited domain:

no limit (default)
mute <-- this is equivalent to Mastodon's "silence" functionality iirc

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

#GoToSocial #PiemelInDeBamiHakHakHak