New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add app.net support #70
Comments
thanks for the research! |
cc @dariusdunlap, who mentioned interest in this. |
Checking out the API docs, I found a few more things that apply: https://developers.app.net/reference/resources/post/replies/
https://developers.app.net/reference/resources/post/search/
https://developers.app.net/reference/resources/filter/
|
if anyone's interested in tackling this, i've written up comprehensive instructions on how to add a new silo to bridgy. feel free to jump in! |
app.net shut down a couple days ago, so we may want to close this issue. the only reason to keep it open i can think of is if anyone is running a separate app.net instance... |
😦 I thought the app.net server was not open source. It's possible someone has written an API-compatible clone of the server software, but I doubt any of them have enough usage to justify adding this to bridgy. |
aha, thanks. tentatively closing. |
Currently the team at app.net has been willing to work with the IndieWeb community, they have microformats2 markup on all of their posts, and support rel-me links for domain verification.
It would be great if bridgy could support app.net as a stopgap until they build in full support for webmention, etc.
API Docs:
Currently app.net posts contain microformats2 markup, although it needs a little bit of cleanup. Bridgy may need to re-create the markup for now until they can clean it up a bit.
The text was updated successfully, but these errors were encountered: