- From: Kagami Rosylight <saschanaz@outlook.com>
- Date: Thu, 14 Dec 2023 00:09:08 +0100
- To: public-swicg@w3.org
- Message-ID: <PAWP189MB2572C3A390133CED8FAC24E6A28DA@PAWP189MB2572.EURP189.PROD.OUTLOOK.COM>
The page source does include application/activity+json: <link href="https://www.threads.net/@zuck/post/C0zXcQmxO77" type="application/activity+json" /> But curl doesn't work as you noted, perhaps it requires some additional things to limit it for internal test? On 13/12/2023 21:35, Evan Prodromou wrote: > > Mike Macgirving pointed out that I'm not using the right media type! I > tried with ld+json and didn't get any traction, though. > > ``` > curl -H 'Accept: application/ld+json; > profile="https://www.w3.org/ns/activitystreams"' > https://www.threads.net/@zuck > > curl -H 'Accept: application/ld+json; > profile="https://www.w3.org/ns/activitystreams"' > https://www.threads.net/@zuck/post/C0zXcQmxO77 > > ``` > > On 2023-12-13 2:07 p.m., Evan Prodromou wrote: >> >> I just saw this post on Threads: >> >> https://www.threads.net/@zuck/post/C0zXcQmxO77 >> >> "Starting a test where posts from Threads accounts will be available >> on Mastodon and other services that use the ActivityPub protocol. >> Making Threads interoperable will give people more choice over how >> they interact and it will help content reach more people. I'm pretty >> optimistic about this." >> >> I haven't been able to probe WebFinger for threads.net accounts, nor >> do Threads URLs reply with Activity Streams 2.0 content. >> >> ``` >> curl -H "Accept: application/activity+json" https://www.threads.net/@zuck >> curl -H "Accept: application/activity+json" >> https://www.threads.net/@zuck/post/C0zXcQmxO77 >> curl -v >> "https://www.threads.net/.well-known/webfinger?resource=acct:zuck@threads.net" >> >> ``` >> >> Has anyone else been able to find signs of this "test" going on? >> >> Evan >>
Received on Wednesday, 13 December 2023 23:09:17 UTC