importer: look into brid.gy

[bradfitz]

I was just shown this:

https://brid.gy/

It could be good for importers.

[snarfed]

ohai @bradfitz! happy to answer any q's, especially if it's over a beer before you head back north. :P

[lindner]

Camlistore could also support webmention/activitypub endpoints.

…

On Mon, Nov 13, 2017 at 4:24 PM Ryan Barrett ***@***.***> wrote: ohai @bradfitz <https://github.com/bradfitz>! happy to answer any q's, especially if it's over a beer before you head back north. :P — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#975 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAF5y4uzF9reOch6tsos-fgGalyWDweTks5s2N2ngaJpZM4Qcj_K> .

[edrex]

#788 mentions bridgy too. It's overspecified since at the time I was all fired up to code it...

[edrex]

(thinking of it as a way to receive social replies to posse posts there)

Generally, I think the way to integrate with indie web stuff is to implement the basic protocols, which tools like bridgy can couple with.

[snarfed]

Generally, I think the way to integrate with indie web stuff is to implement the basic protocols, which tools like bridgy can couple with.

agreed!

[edrex]

I think an ultra trimmed down version of #788, implemented as a PerKeep "app" modeled after the publish app, would be a great exercise, but this issue is about the other end: getting PESOS posts and replies imported into PerKeep.

We currently have a facility for that via native Go importers, but for example the Twitter one only imports your tweets, not replies.

If support for listening for webmention proxies from Bridgy were implemented, and the reply structure were properly captured as references in the Perkeep data model, then this "Microblog" app could use search to efficiently listen for new replies for cache invalidation purposes.

@bradfitz is this kind of what you were thinking of?
@snarfed any pitfalls for younger players i'm not seeing?

[edrex]

This becomes really intersting when you bring all the bits together to implement POSSE reply inlining:

1. Publish an h-entry formatted post via Microblogging (indieweb) #788.
2. Share the post's public URL in a tweet/fb post.
3. Auto-import your remote post via Bridgy
4. Get replies.
5. Auto-import the replies via Bridgy.
6. In Microblogging (indieweb) #788 post page, query PerKeep for
   1. Shares of this page URL on remote sites (webmentions)
   2. Replies to those shares.
7. See them rendered inline on the post page.

(manual steps in bold)

[edrex]

Steps 3 and 5 are the only pieces that this issue need worry about.

To support 6. the indexer will need to index URLs from the imported post content (seems like a good idea anyway, not sure if there's an issue for that already).

I'm going to work on cleaning up #788 to keep this issue focused on just the Bridgy integration.

[snarfed]

this all sgtm!

users will need to sign up each of their social network accounts with bridgy. you can actually direct them through this from perkeep, if you want, and they'll return afterward: https://brid.gy/about#registration-api

they'll also need to put their perkeep microblog's domain in their social network profile: https://brid.gy/about#profile-link

after that, bridgy does steps 3 and 5 automatically, ongoing. the perkeep microblog just needs to accept webmentions.

bridgy can also POSSE an h-entry post into some social networks, if you want: https://brid.gy/about#publish

[edrex]

If this all sounds a bit too "sketch on a napkin", here's an example of POSSE reply inlining from Facebook and Twitter using a self-hosted Known instance and Bridgy.