@noellabo I have a question about the "Mutual followers only" option. Is it compatible with other regular Mastodon instances?
Besides, last year you said that "circles" relied on some standard that was not implemented in the vanilla Mastodon, so "circle" was not compatible with vanilla Mastodon instances. Is "circle" compatible with vanilla Mastodon today?
@noellabo If you are developing the Group feature you may be interested in this notice.
gup.pe has stopped working for the new version of Mastodon since probably August, so if fedibird.com cannot receive messages from gup.pe, it is not a bug in the Fedibird.
QT: https://social.coop/@datatitian/105080638741179415
@sandbox_jp test
@noellabo
May I ask some questions about hashtag relay?
1. Is there anyway to reject an existing domain? For example, bad.com has already joined the relay, but I don't know how to send a rejection message to it so that they can stop sending messages to the relay. Suppose that bad.com is a normal Mastodon instance.
2. Do I have to manually create an activity.json to do something like above? Is there any convenient way to compose a valid activity.json?
Thanks!
@noellabo @noellabo Thanks! One more last question (sorry to bother you again):
There are lots of options for the hashtag relay. Am I supposed to manipulate the options in directly in redis?
For example, if I want to block a bad.com (a Mastodon instance), I should use redis-cli with command
SADD deny_domain:bad.com "bad.com@bad.com".
Is that correct?
@noellabo Thanks! May I also ask some questions about your hashtag relay?
I am trying to setup a hashtag relay for my community.
1. Is selective-relay the same as hashtag relay? Is "hashtag only" filter hard coded in the code or should I use some config files to implement this?
2. If an instance admin has set AUTHORIZED_FETCH=true, will that instance work with the relay? I think the message from the instance may lack a linked-data signature.
@noellabo @circledev I have looked through the code.
To me Line 48 of process_mentions_service.rb seems to be causing the trouble.
If a group member is local then the mention will always go through LocalNotificationWorker, but that worker does not handle "silent" mentions.
Remote circle members do not receive notifications, but local members will.
@noellabo @circledev I haven't tested on Fedibird yet and am not sure if it's the same for Fedibird. My development server runs a slightly different version of code from the Fedibird's.
@noellabo @circledev On my testing server the recipient always receives a notification when someone that they follow posts something in a circle. I think the backend probably treats circle posts like DMs. But I don't think it's a good idea to send notification for every circle post.
@noellabo May I ask a question about Group Timeline? What is the difference between
using a Group Timeline
and
just following a group actor from a vanilla Mastodon instance?
Thanks!
Test! @mastodev