Gregory's ServerPixelfed is federating with Threads!
 28 comments
 Evan, that, and they don't even have /.well-known/host-meta set up to properly redirect it.  > > that, and they don't even have /.well-known/host-meta set up to properly redirect it. I don't think  WebFinger lets us take an ID like name@domain.example and get an actor endpoint https://domain.example/some/path/to/idnumber.jsonld . The format of the actor endpoint is implementation-dependent, so the WebFinger lets us have a nice little ID that is easily recognizable. @grishka The problem (?) is that I could configure my WebFinger server to point to someone else's actor endpoint, which would be misleading. So if evan@domain.example points to https://whitehouse.example/users/potus, it would make it seem like evan@domain.example is the right shortcut for getting to the President of the United States's ActivityPub endpoint. (It will happen.) It's not *that* big a deal, but it's a little bit of a problem. @grishka What we need is a way for the AP descriptor to say, "these are valid Webfinger strings to use for this account." There's not a way to do that in the AP standard (yet; I'm going to start working on a FEP for it). @grishka The way Mastodon hacked around this, and other implementations have copied, was by taking another element of the actor, `preferredUsername`, and the domain part of the actor endpoint, and making a Webfinger id out of those two. So, in the above example, it'd make a Webfinger ID out of potus@whitehouse.example. @grishka It then does the Webfinger lookup again with that new Webfinger ID, and checks that it points to the right Actor endpoint. It then stores this webfinger ID as the right one to use for this actor from now on. @grishka So, the problem I'm seeing with threads is that its webfinger IDs are on the threads.net domain, like mosseri@threads.net. But the actor endpoints are on the www dot threads.net domain (I typed that out because threads keeps eliding out the www), so all the services are going through the dance I described above, and ending up with "corrected" Webfinger IDs like mosseri@www.threads.net. @grishka In general, we just want to use the bare domain name if at all possible, at least for the actor endpoint. Most activitypub implementations rely on webfinger anyway and I see that threads.net's webfinger solves the problem by returning proper URI even if I mistakely request But www subdomain is desirable for cookies isolation in cases when site has multiple other subdomains for different purposes. > > Smithereen too, by the way Their url top.ofthe.top, you need to sign your get request. I already sign mine for an unrelated reason (private groups & privacy settings), so it just worked for me. Yes, signing get requests helped, thanks. This also fixed federation with gotosocial, they require get requests to be signed too (I was lazy to fix it). But in case of required signature threads.net should respond with error like  @dansup Congrats on this! Did Federation just work through the power of friendship and ActivityPub? Or did you have to do any extra work to make the connections go? Of you learned any lessons in getting this to interop, it would be amazing to hear what you did. @dansup Thats awesome news. Thank you for this info. Hopefully it means that there’s not a “Threads dialect” of ActivityPub, and if I can communicate with PixelFed I shouldn’t be too far away from talking to Threads, too.   @dansup Absolutely wild! Though it's kinda jarring to have the usernames end in @/www.threads.net and I hope they make it just threads.net in the future.   |
@dansup that www. is going to be a problem. I hope they clean that up.