Ryan Barrett

got it! bridgy actually converts silo interactions both from _and_ to webmentions, both directions. most people know it for the former, eg converting twitter @-replies and likes to webmentions, but...

related: #270

cc @phyks, who's expressed interest. https://wiki.diasporafoundation.org/Federation_protocol_overview#ActivityStream_of_public_posts says you can get posts (and other data) as ActivityStreams, and that the reference implementation includes an API. yay.

thanks for the research @Phyks! btw, pubsub definitely isn't a requirement for bridgy, whether PuSH or anything else. we currently poll the four silos we do support, so I'd be...

showing only reply/like/reshare counts, and not the actual contents, is how the ActivityStreams schema works, so i'm not too surprised about that. it definitely seems like there should be some...

that does sound disappointing. :( I wonder if part of it is just that the project hasn't been very active for a while, since iirc the founders/leaders left a while...

if anyone's interested in tackling this, i've written up [comprehensive instructions on how to add a new silo to bridgy.](https://github.com/snarfed/bridgy#adding-a-new-silo) feel free to jump in!

fwiw, i'm now likely to work on diaspora support in https://fed.brid.gy/ first (which is close!), and less likely to do it here in bridgy.

thanks for the thoughts @vipickering! makes sense. there's definitely been plenty of discussion of this check-in vs post-with-location distinction over the years: * https://indieweb.org/checkin#just_a_note_with_a_location * https://indieweb.org/post-type-discovery#Feature_consideration_checkin out of curiosity, do...

cool! i see _REST API and JSON views_ in the _What's coming up?_ section in the right sidebar on the https://upcoming.org/ home page, which implies it's not there yet. bridgy...