search

snarfed / bridgy

📣 Connects your web site to social media. Likes, retweets, mentions, cross-posting, and more...
https://brid.gy
Creative Commons Zero v1.0 Universal
726 stars 52 forks source link

Silo request: dev.to #874

Open jamietanna opened 5 years ago

jamietanna commented 5 years ago

For i.e. development-focussed posts it'd be cool for POSSE to dev.to.

jalcine commented 5 years ago

Looks like https://dev.to supports publishing via RSS. Which is okay if you can generate a specific feed of posts you’d want to have on dev.to, then that’d work. https://dev.to also doesn’t seem to have a public API so syndication is going to be tough.

(Originally published at: https://v2.jacky.wtf/post/3f7ec34b-9303-47de-9ff2-2ccf3d34b352)

siakaramalegos commented 4 years ago

It looks like they have a beta API. Not much in it but could grab counts https://docs.dev.to/api/#operation/getArticleById

snarfed commented 4 years ago

thanks @siakaramalegos! sadly we can't really do anything with counts alone, but feel free to file a feature request with them to add individual comments, reactions, etc to their API.

Ryuno-Ki commented 4 years ago

That would be https://github.com/thepracticaldev/dev.to I guess.

snarfed commented 4 years ago

thanks @Ryuno-Ki! https://github.com/thepracticaldev/dev.to/issues/4474 seems to say that they actually do expose individual comments, reactions, etc. in the API, they just haven't documented those endpoints yet.

siakaramalegos commented 4 years ago

Oh that's really cool. Thanks for sharing. I don't mind helping on this though I don't have experience in your codebase yet.

snarfed commented 4 years ago

thanks! here are instructions for adding a new silo. it's not a small project, but it's definitely doable! first step is to add it to oauth-dropins.

siakaramalegos commented 4 years ago

I'm a little confused, but I think Oauth isn't yet public https://docs.dev.to/api/#section/Authentication

But reading from Dev seems to be public only needs a token to grab your own data without the need for a secret key.

Edit:

So maybe not ready for Bridgy yet, but I'm going to run the different API calls and report back with sample data.

siakaramalegos commented 4 years ago

Documenting in gist here https://gist.github.com/siakaramalegos/37eede3c20799912ed6bcd04e0da3e59

snarfed commented 4 years ago

got it! we'd then need a separate signup form to point new Dev users to where to get their token, and then let them enter it into Bridgy to sign up, similar to how the current Mastodon and Instagram signup flows on https://brid.gy/ work. that can come a bit later though. if we don't need oauth-dropins for Dev, you can skip ahead to adding it to granary.

jamietanna commented 4 years ago

It looks like https://docs.dev.to/api/#section/Authentication shows "OAuth2 authentication is still in private alpha." so hopefully could be available soon! We may be able to get on the private beta?

(Originally published at: https://www.jvt.me/mf2/2020/06/uwbrn/)

siakaramalegos commented 3 years ago

Posted on Forem to request the feature for Dev.to webmentions. Some of you are more experienced, so would be good to get your feedback there: https://forem.dev/thegreengreek/enable-webmentions-o0c

Apparently they are moving away from GitHub issues for feature requests and it needs to be done there.

iamschulz commented 3 years ago

Grabbing comments from their API doesn't require authentication: https://dev.to/api/comments?a_id=185402

As I understand it, it should be possible to build a silo without publishing support with that.