GoToSocial

The relay https://relay.toot.io, and indeed any Activity-Relay service that uses the up-to-date version 2.0.11, now works correctly with GoToSocial:

https://github.com/yukimochi/Activity-Relay/issues/117

If anyone is still having trouble connecting to services running the Activity-Relay software, you can:

1. Gently poke the admins of those relays to update to v2.0.11, which is the only version currently that works with GtS.
2. Then as GtS admin you can then try removing all previously-created connections to the relay (pushes and subscriptions), and recreating them in order to re-send the Follow activity. You should receive an accept within a few seconds if all goes well.

If you want posts to actually show up on the federated timeline of your instance, don't forget to either tick "match posts by default" when creating the subscription, or create appropriate relay matchers to pick which posts you want your instance to store + timeline.

#GoToSocial

HELLO here's a little video of me creating a relay actor on a #GoToSocial instance, then subscribing my own instance to it.

Here's what I do in the video:

1. Create the relay actor by filling in the form in the settings panel.
2. Show off the relay actors overview and details page.
3. Show off the relay actor account web view.
4. Go to the settings panel section for relay subscriptions and create a new subscription targeting the relay I just created.
5. Go to the relay actor follow requests tab, and accept the follow request.
6. Show the follower in the followers tab.
7. Show on the web view that the relay actor account shows 1 connection to localhost:8080 (the testing instance).

None of this is in main branch yet, it's just on the branch i'm working on.

The relay https://relay.toot.io, and indeed any Activity-Relay service that uses the up-to-date version 2.0.11, now works correctly with GoToSocial:

https://github.com/yukimochi/Activity-Relay/issues/117

If anyone is still having trouble connecting to services running the Activity-Relay software, you can:

1. Gently poke the admins of those relays to update to v2.0.11, which is the only version currently that works with GtS.
2. Then as GtS admin you can then try removing all previously-created connections to the relay (pushes and subscriptions), and recreating them in order to re-send the Follow activity. You should receive an accept within a few seconds if all goes well.

If you want posts to actually show up on the federated timeline of your instance, don't forget to either tick "match posts by default" when creating the subscription, or create appropriate relay matchers to pick which posts you want your instance to store + timeline.

#GoToSocial

AHA!

Gotta add buttons now...

#GoToSocial #Piss

Relay actor stuff is coming along it's coming along!

In the settings panel of the branch I'm working on, admins can now create, update, and delete relay actors (and their matchers), choose whether to manually approve follow requests, etc.

Next I'm gonna add some more panels for managing follow requests, removing followers, and creating and removing blocks.

#GoToSocial #Relay #Piss

DID YOU KNOW: In #GoToSocial, if you go to your account settings and change your layout to "Gram-style", you can set the web view of your profile to show an instagram-like grid of photos to visitors.

This is handy for folks that primarily post photographs or other media and want to highlight that when people visit their profile on the web :)

We wrote this feature quite a while ago but not that many people know about it!

DID YOU KNOW: In #GoToSocial, if you go to your account settings and change your layout to "Gram-style", you can set the web view of your profile to show an instagram-like grid of photos to visitors.

This is handy for folks that primarily post photographs or other media and want to highlight that when people visit their profile on the web :)

We wrote this feature quite a while ago but not that many people know about it!

The positive result of the #Codeberg membership votes to ban so-called "vibe-coded" projects from Codeberg (see here) makes us very proud to continue hosting #GoToSocial on @Codeberg!

Following the votes and changes to the terms and conditions, Codeberg has written up their stance on LLM's and "vibe-coded" projects:

Although often well intentioned, sharing the result of an prompt and calling it "libre software" does not make the world a better place. Codeberg is not and does not want to be a place to dump such generated single-use software that no one else will ever look at. We are a place for people to collaborate and improve software together. Within this context, the recent votes can be understood as a reconfirmation of those principles: As we want to center on human collaboration, we will not actively support or engage in the creation of LLMs and will not put our limited resources to use for storing single-use software that would pollute our FLOSS commons.

The blog post is well-written, well-sourced, and worth reading in full:

https://blog.codeberg.org/protecting-our-floss-commons-from-llms.html

Since GtS has a very pointed anti-LLM policy in our Code Of Conduct, it's particularly pleasing to us that Codeberg is now pointing out that users are no longer welcome on Codeberg if they "[send] LLM contributions in violation of project's custom policies". Happily for us, this has not been a recurring problem on GtS as we tend to give off vibes that keep slop-fondlers at arm's length, but it's good to know that our anti-"ai" policy has institutional support now in case it becomes more of a problem in future.

If you want thank Codeberg by supporting them with membership and/or donations you can do so here: https://join.codeberg.org/