Notices by André Menrath (linos@graz.social)

@pfefferle @castopod What do you mean by does not seem to federate the audio properly? I can playback it within the Mastodon UI. The media also gets loaded from my server, it is cached.

@pfefferle If you should be interested in ActivityPub and Podcasts as well: @castopod federates a Note with the audio as attachment [1] and links to another object of type PodcastEpisode [2] which has much more MetaData. (...because does ignore all unknown object types, and the devs didn't try to add that one to the list of converted object types yet.)

[1] https://podcast.graz.social/@demo/posts/f3fca804-5e4c-4fe0-8694-cfb3c7fadcc5
[2] https://podcast.graz.social/@demo/episodes/das-yamaha-portasound

@pfefferle @antiaall3s You mean that whether publishing via ActivityPub is not enough covered by coupling it to the visibility of the post? Concrete examples of use cases you have in mind would help a lot. Could you find time and elaborate more? That would be great! Thank you!

@pfefferle To my knowledge this is not documented yet, but what I know:

1. Try Fetching application actor from NodeInfo (fallback, use the @relay@instance.tld actor) [1]

2. Do validations (e.g. type must be either Group or Application) [2]. Here also the faulty outbox, which I provided that small fix for recently led to problems.

Other than that, the process seems to be no different.

[1] https://framagit.org/framasoft/mobilizon/-/blob/main/lib/federation/node_info.ex#L17

[2] https://framagit.org/framasoft/mobilizon/-/blob/main/lib/federation/activity_pub/relay.ex#L47

Maybe I should document it... :)

@pfefferle This is an example from the relevant Mobilizon debug logs:

1. Fetching application actor from NodeInfo
2. Getting or fetching actor by URL
3. Fetching NodeInfo details for domain
4. Going to get NodeInfo information from URL
5. Found nodeinfo information for domain
6. Ready to save instance actor details
7. Saved instance actor details for domain
...

I currently don't have more, cause again here I stumbled into problems with local CAs, which should be fixed, but there is a bug.

@pfefferle You maybe noticed, that also groups could get followed. The idea was that one could either enter e.g. @notiz.blog, or the URL of an group actor too. But it is not implemented yet. At least it never worked for me, and reading Elixir code is hard for me.

Folgeempfehlung, wenn ihr mehr über queer-feministische Themen/Events in #Graz mitbekommen wollt: @qufo_graz

Der Account ist ziemlich #NeuHier. Zeigen wir ihnen, dass das Fediverse lebt.

@pfefferle @vsg_DE Hat mich allerdings auch irritiert, dass es nicht so war! ;)

@pfefferle @django But isn't that only needed due to implementations misusing the id for the url field?

E.g., Mobilizon does not seem to distinguish between id and url atm, at least that is what my conclusion was by reading the source. But anyway I think we should push others to fix their non-spec compatibility bugs than to think of workarounds from the beginning.

I see, I have to study the specs again, cause I am not sure about the usage of both.

@django @pfefferle Interesting. Hmm.

@jenniferplusplus @rimu Thanks for your answers but I think we mean something different. My concern was about undoing the "Accept of the Follow" not the Follow. The point of view is the actor receiving the follow, not the actor following another. I think one should not send an Undo of an activity one hasn't issued oneself.

FYI: I found this answer interesting: https://fediversity.site/item/900328af-5252-4198-aa8b-b97bd541bbb8

Question for my fellow #FediDevs:

In #ActivityPub when removing a previously accepted follower, should one send a 'Reject' of the 'Follow' or 'Undo' the previously sent 'Accept'. Or is both valid?

@jan @pfefferle Can Mastodon fetch the post directly? Try copy-pasting the Permalink in the search field.

@pfefferle @blog No! :) Just amazing. https://webrocker.de/2005/08/

@blog And you may notice: the fediverse profile of your blog says: Joined 2005!

@pfefferle Are you finally approaching issue #1? (: The group actor, as well as the relay actor, is also one of our tasks to solve in our WordPress event federation project, we will start working on in july (with support from to NLnet).

Whereas the relay actor towards mobilizon has a fixed naming scheme, our plans also have been to make the group actor customizeable and have the admin interface inform users about naming conflicts.

@Gargron Can you point me to which startsite (without being logged in) you have set up at mastodon.social? We want that as well for our instance :) #MastoAdmin