Create services to use the downstream APIs from Interactions, both to prove the pattern and serve as exemplars for others. The services:
[ ] Post new releases to social media, triggered by webhooks
[ ] Periodically submit source repository stats: stars, commits, activity in 30/90/365 days, number contributors, number of issues, etc.
Other ideas to consider, or to inspire anyone to build on the platform:
A service that downloads extensions for each release and smoke tests them on a variety of OSes and Postgres versions and builds a matrix reporting the results on the web. It might submit simple stats (pass/fail/skip counts), a badge indicating the overall result, and a link back to the matrix page.
A variant of the smoke testing service that tests upgrades from earlier versions and reports stats for successes and failures and produces diffs for the changes.
A service that allows users to rate extensions or write reviews. It might submit a link to the discussion along with some stats like average rating or comment count. This can help users evaluate the quality of an extension.
A service that downloads extensions for each release and scans them for security vulnerabilities. It might submit some basic stats (advisory counts, quality badge) and a link to a deeper assessment. It could even be a paid service, charging customers for access more information, or providing a private registry with only low-vulnerability extensions.
A service that curates and classifies extensions according to its own priorities and systems. It might submit back the main classification term, or social up/down votes for classifications from users.
Create services to use the downstream APIs from Interactions, both to prove the pattern and serve as exemplars for others. The services:
Other ideas to consider, or to inspire anyone to build on the platform: