pfefferle,
@pfefferle@mastodon.social avatar

@linos do you have a link to a documentation of the follow/approval process on application level, that is used by ?

linos,
@linos@graz.social avatar

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

  1. Try Fetching application actor from NodeInfo (fallback, use the @relay 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... :)

linos,
@linos@graz.social avatar

@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.

linos,
@linos@graz.social avatar

@pfefferle You maybe noticed, that also groups could get followed. The idea was that one could either enter e.g. @notiz.blog@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.

pfefferle,
@pfefferle@mastodon.social avatar

@linos @notiz.blog@notiz.blog thanks, that helps a lot! :)

mro,
@mro@digitalcourage.social avatar

Hi @linos, was bedeutet
> 1. Fetching application actor from NodeInfo

wieso nodeinfo? Ich dachte entweder oder direkt

Was geht ab?

linos,
@linos@graz.social avatar

@mro https://codeberg.org/fediverse/fep/src/branch/main/fep/2677/fep-2677.md

The problem was instance-to-instance following only knowing a domain. There would have been other possibilities, people on SocialHub also discussed why that FEP might not be the best solution. Maybe just having https://example.tld/ resolving to that actor profile could work too. I haven't spend too much time in weighting all pros and cons, but as adapting to other solutions is not that much work...

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • PowerRangers
  • DreamBathrooms
  • everett
  • magazineikmin
  • InstantRegret
  • ngwrru68w68
  • Youngstown
  • Durango
  • slotface
  • rosin
  • GTA5RPClips
  • tester
  • kavyap
  • thenastyranch
  • provamag3
  • mdbf
  • osvaldo12
  • ethstaker
  • vwfavf
  • cubers
  • normalnudes
  • tacticalgear
  • khanakhh
  • cisconetworking
  • modclub
  • Leos
  • anitta
  • megavids
  • All magazines