-
Notifications
You must be signed in to change notification settings - Fork 52
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
POSSE events to Upcoming.org (no API yet) #740
Comments
Example of an event on Upcoming I'd like to RSVP to: https://upcoming.org/event/homebrew-website-club-san-francisco-246bjt5v5f |
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 publish generally only uses APIs, not form submit scraping, so we'd probably wait for the API. fingers crossed that arrives soon! |
Alternately, upcoming.org could support importing events by parsing the event Microformats at the existing URL. Related issue: upcoming/upcoming-www#49 |
doesn't seem like upcoming is actively developed any more. roadmap on the home page right side bar seems pretty much unchanged, including API. github commits (and twitter) show the last meaningful development and activity was spring 2017. only a handful of minor changes and tweaks since then. |
Same, more or less, 2.5y later. A few scattered commits on GitHub, but no API or other meaningful progress on the roadmap. |
Same, over 6 mos later. Seems like Upcoming is abandoned. Closing. |
Now that upcoming.org is live and I think has an API (or fairly straightforward form submission "API" at https://upcoming.org/event/add) it should be possible to have Bridgy Publish support POSSEing Indie events and RSVPs to Upcoming!
And similarly, Bridgy backfeed RSVPs back from Upcoming (ok to split into separate issue)
E.g. https://upcoming.org/event/homebrew-website-club-san-francisco-246bjt5v5f backfeed to: http://werd.io/2017/homebrew-website-club-april-5-2017 (perhaps extra challenging since POSSE copy was added manually not by the creator of the original post!)
If we get this working, this would be the first event destination where it is possible to fully automatically POSSE to it!
The text was updated successfully, but these errors were encountered: