Post 9sPt3oz8CEocrGOc5I by nightpool@cybre.space
(DIR) More posts by nightpool@cybre.space
(DIR) Post #9sFIEo0qVpAN8vyPPU by grishka@mastodon.social
2020-02-20T17:07:31Z
1 likes, 0 repeats
@liaizon @wakest okay, this was the missing piece to this puzzle, now I know why Mastodon keeps requesting this host-meta thing. I think I need an XML parser now.This definitely strays from the AP spec.
(DIR) Post #9sFIEoldhqb3U3rmLY by liaizon@social.wake.st
2020-02-20T17:08:31Z
0 likes, 0 repeats
@grishka I found a copy of the old documentation for ithttps://github.com/moko256/mastodon-docs/blob/master/Running-Mastodon/Serving_a_different_domain.md
(DIR) Post #9sFIEpW4vBk9o5arjM by liaizon@social.wake.st
2020-02-20T17:09:20Z
0 likes, 0 repeats
@grishka @nightpool do you happen to know why this isn't in the current documentation anymore?
(DIR) Post #9sFIEpynCQiDF91nUG by grishka@mastodon.social
2020-02-20T17:10:50Z
0 likes, 0 repeats
@liaizon @nightpool ¯\_(ツ)_/¯Actually not the AP spec. The AP spec doesn't deal with any of the username stuff, it assumes every identifier is an URI.
(DIR) Post #9sFIEqPNbZymZbT1vc by nightpool@cybre.space
2020-02-20T17:38:21Z
1 likes, 0 repeats
@grishka @liaizon all of this stuff is spec'd out by webfinger! https://tools.ietf.org/html/rfc7033
(DIR) Post #9sOcseE24F2TsT3XU0 by nightpool@cybre.space
2020-02-20T17:37:10Z
0 likes, 0 repeats
@liaizon @grishka it was a pretty niche usecase and made it very easy for inexperienced admins to shoot themselves in the foot
(DIR) Post #9sOcseeGUi1TBpKUN6 by clacke@libranet.de
2020-02-25T12:34:39Z
0 likes, 0 repeats
@nightpool @liaizon @grishka Niche? Mastodon fails to follow users that don't have a webfinger.> Mastodon will ignore actors without WebFinger (it performs verification for username@domain ownership), and Mastodon will ignore actors without an inbox.https://github.com/tootsuite/mastodon/issues/4906#issuecomment-328844846Totally against spec and closes off a whole bunch of interesting usecases but there you go.WebFinger was a part of OStatus, the protocol Mastodon was originally built around.
(DIR) Post #9sOczkAMNVXeKUioqW by clacke@libranet.de
2020-02-25T12:35:56Z
0 likes, 0 repeats
@nightpool @liaizon @grishka Oh wait, you mean supporting webfinger pointing to a different host is niche.Perhaps, but it is supported. It's just a reference.
(DIR) Post #9sOdH11AybZ5W9f6iu by liaizon@social.wake.st
2020-02-25T12:37:30Z
1 likes, 0 repeats
@clacke @nightpool @grishka we *must* have documentation about this still because there are many instances that set it up this way when there *was* documentation for this feature.
(DIR) Post #9sOdH39l1fcM9LgzNQ by Nut@shitposter.club
2020-02-25T12:39:05.501119Z
0 likes, 0 repeats
@liaizon @clacke @nightpool @grishka
(DIR) Post #9sOhdXSjQfEgKVXwDA by grishka@mastodon.social
2020-02-25T12:50:27Z
0 likes, 0 repeats
@liaizon @clacke @nightpool I mean I had no idea this was a thing at all until you pointed out.
(DIR) Post #9sOhdXwrcdL3pxe0B6 by liaizon@social.wake.st
2020-02-25T13:07:20Z
1 likes, 0 repeats
@grishka @clacke @nightpool If someone hadn’t deleted a whole page out of the documentation you would have already known about it :)
(DIR) Post #9sOhdYTTfNQVT6u30q by drq@mastodon.ml
2020-02-25T13:12:17Z
1 likes, 0 repeats
@liaizon @grishka Here's a great list of articles about AP in practicehttps://flak.tedunangst.com/post/ActivityPub-as-it-has-been-understoodI think, it might be useful@clacke @nightpool
(DIR) Post #9sPt3mxHk89OYxW6vg by nightpool@cybre.space
2020-02-25T13:46:16Z
0 likes, 0 repeats
@liaizon @clacke @grishka documentation doesn't stop people from writing code with bugs. we already have a thorough test suite around webfinger, including (as I understand it) test cases for separate local and web domains. But it looks like one part of this codepath was untested and had bugs in this area. I disagree that the fact that we still support it means we should add documentation telling people how to set it up. the two things are unrelated.
(DIR) Post #9sPt3nvY84M9ZriErY by liaizon@social.wake.st
2020-02-25T13:54:31Z
0 likes, 0 repeats
@nightpool @clacke @grishka it could easily be mentioned while being noted that its not a recommendation and can cause issues. Having it not included in the documentation now means all the people who read the documentation come to the conclusion that mastodon profile uris only work one way and this is not true.
(DIR) Post #9sPt3oz8CEocrGOc5I by nightpool@cybre.space
2020-02-25T13:56:21Z
0 likes, 0 repeats
@liaizon @clacke @grishka our messages crossed, but mastodon's documentation isn't a spec and shouldn't be mistaken for one. just because people might come to the conclusion that mastodon's profile URIs work one way doesn't mean anything. there's more software in the world besides mastodon
(DIR) Post #9sPt3pSuPWdQLcKOUy by grishka@mastodon.social
2020-02-25T18:28:13Z
0 likes, 0 repeats
@nightpool @liaizon @clacke but maximizing the compatibility between software that interoperates is important. When things don't work, users (rightfully) blame developers.
(DIR) Post #9sPt3pvyfRt3nlvbo8 by clacke@libranet.de
2020-02-26T03:10:35Z
0 likes, 0 repeats
@grishka @nightpool @liaizon It is a difficult situation that there is no spec for the Fediverse and that the ActivityPub spec is insufficient for compatibility with the majority of instances and users.The LitePub spec was somewhat supposed to achieve this, among other aims, but I haven't heard about it for quite some time and don't know the status.