Domain names feed for getting notifications of new issues

[tobiastom]

It would be awesome for site owner if I could register on the project, specify to which sites I'm responsible (including a verification), and then get notified once someone posts an issue about one of the sites.

Currently I have to go back to the project each and every time and check if someone might have created an issue. I don't assume many people will do that…

[calexity]

Thanks for the feedback @tobiastom - this is an interesting idea. Adding it to my notes to consider how to implement.

[karlcow]

@tobiastom What would be the trigger? The domain name?

Would a feed of issues by domain names solve your concerns?
Something ala

• http://webcompat.com/domains return a list of all domain names currently available (text/html, application/json and application/atom+xml)
• http://webcompat.com/domains/com.example return a list of all issues for this domain name (text/html, application/json and application/atom+xml) with the date of opening, date of last comment, date it has been closed.

[karlcow]

Related to #132

[tobiastom]

Domain name would be ok for me. I just would like to get a notification when someone reports a problem for one of my sites, apps, whatever. So domains would be ok.

I'd love to get that per RSS! One important thing: when there is no issue for my domain example.com, http://webcompat.com/domains/com.example might be a 404, so I could not subscribe it.

Also, what would happen if I subscribe to com.example and an issue is raised for lala.example.com?

[calexity]

I love this feature because it makes outreach less work!

[karlcow]

@tobiastom

Also, what would happen if I subscribe to com.example and an issue is raised for lala.example.com?

I guess as a first approximation, we could make it that it matches both, but if someone is entering http://webcompat.com/domains/com.example.lala, it gets only these.

Also to determine if we should do: http://webcompat.com/domains/com.example.lala or http://webcompat.com/domains/lala.example.com, not sure what is easier or more logical for people.

[tobiastom]

I would get with the harder to understand one http://webcompat.com/domains/com.example.lala because then I could subscribe com.example including all sub-domains. I could not do that with http://webcompat.com/domains/lala.example.com.

[ChaseOnTheWeb]

Perhaps it could use a cookie-like syntax, where

• http://webcompat.com/domains/example.com would show only issues for example.com (and maybe www.example.com since it's commonly a synonym), but
• http://webcompat.com/domains/.example.com (with leading dot) would show example.com and all subdomains.

This would allow flexibility without needing to reverse the domain name (which I know is common in certain programming ecosystems, but probably not as familiar to Web practitioners in general).

[tobiastom]

Would be ok for me. Also `http://webcompat.com/domains/example.com?include-subdomains' wouldn't be a problem for me.

[hallvors]

I think we should have both E-mail subscription ("send me an E-mail if there's an issue for site x") and RSS. Maybe those should be separate bugs.

[miketaylr]

cc @deepthivenkat

[miketaylr]

We can include a <link rel=alternate> in the head of the page that lists the domains, e.g.,<link rel="alternate" type="application/atom+xml" href="http://www.la-grange.net/feed.atom"> and this will allow feed readers/software to subscribe. See http://microformats.org/wiki/rel-alternate

[miketaylr]

We can create a route like https://webcompat.com/feeds/facebook.com that shows the list of related issues, etc.

[tobiastom]

@miketaylr That would be awesome.

[miketaylr]

Let's close this in favor of #132.