Matt Cowley
Matt Cowley
This is not an issue on your end, it is an issue on our end as I explained in my previous reply.
We don't really make subdomain determinations prior to having a PR created and being able to see the actual content in question. Generally though, if a site is just _using_/_built...
> Wouldn't the solution to that be to copy the cloudflare agent filtering rules down to NGINX for the requests to the direct.nodejs.org. `direct.nodejs.org` isn't proxied through Cloudflare, so that...
Ah yeah, we could move the restrictions to NGINX as well as Cloudflare (or remove them from Cloudflare at that point). It still leaves the origin exposed to the world...
I don't believe this is stale, as NGINX is still serving some routes via Cloudflare.
👀 I'm not sure why you'd need access particularly, until we're ready to push the changes live? All they give us are very limited slots for HTML, and then global...
I think this'd be fine for anyone to work on, but I'd definitely encouraging sharing thoughts and mockups here before putting a large amount of work into code.
As vey basic groundwork relates to this, I've got a PR open that lets us track VoD URLs as well, so that notifications can link to VoDs after a certain...
@pjeweb, your thoughts here would be good? Given how little we use notifications for announcements, and how frequently they're used for streams, I wonder if we can simplify this quite...
I think leaving announcements as it is for now is fine, and focus on improving the stream notif use-case. If/when collabs pick up steam again, it might be good to...