- From: Cristiano Longo <cristianolongo@opendatahacklab.org>
- Date: Thu, 14 Dec 2023 15:12:21 +0100
- To: public-swicg@w3.org
- Message-ID: <1126b779-d24b-49bd-80f6-c61b6232a8b0@opendatahacklab.org>
On 14/12/23 02:43, Ben Savage wrote: > Hi everyone, > > Ben Savage here from Meta. Just a few quick points: > > 1. This test is not yet started (debugging some last technical issues > together with Mastodon engineers) > 2. Only a few accounts will be a part of this initial test. My > Threads account (https://www.threads.net/@btsavage) will be one of > those and I'm happy to make test posts to help people who want to > work on Threads integration. > 3. We will share details about how to test soon, once we iron these > issues out. > > > --Ben > But requesting content with activity+json mimetype I get a redirect to https://www.facebook.com/unsupportedbrowser > ------------------------------------------------------------------------ > *From:* Kagami Rosylight <saschanaz@outlook.com> > *Sent:* Wednesday, December 13, 2023 11:09 PM > *To:* public-swicg@w3.org <public-swicg@w3.org> > *Subject:* Re: Threads testing federation via ActivityPub > 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 > ZjQcmQRYFpfptBannerStart > This Message Is From an Untrusted Sender > You have not previously corresponded with this sender. > ZjQcmQRYFpfptBannerEnd > 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.w3.org/ns/activitystreams>' >> https://www.threads.net/@zuck <https://www.threads.net/@zuck> >> >> curl -H 'Accept: application/ld+json; >> profile="https://www.w3.org/ns/activitystreams" >> <https://www.w3.org/ns/activitystreams>' >> https://www.threads.net/@zuck/post/C0zXcQmxO77 >> <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 >>> <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 <https://www.threads.net/@zuck> >>> curl -H "Accept: application/activity+json" >>> https://www.threads.net/@zuck/post/C0zXcQmxO77 >>> <https://www.threads.net/@zuck/post/C0zXcQmxO77> >>> curl -v >>> "https://www.threads.net/.well-known/webfinger?resource=acct:zuck@threads.net" >>> <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 Thursday, 14 December 2023 14:12:30 UTC