Closed johnozbay closed 4 years ago
Hello! Thank you for opening your first issue in this repo. Itβs people like you who make these host files better!
P.S. Seems like the same thing's happening to RoamResearch and users have been talking about it on their reddit as well.
Thanks John!
Ping @jawz101.
Thanks a million for the quick response Steven! ππ» Deeply appreciated!
removed. thank you
Many thanks for the quick turnaround time both ππ» Stay safe and well βπ»
Thanks everybody. This is live and online in the latest release.
Massive thanks for this & the quick fix-time!
Hey there @StevenBlack & @jawz101 ππ»
This week we've started receiving support messages from tons of users telling us that they can't access our service while using PiHole, AdAway and others using these lists.
Looks like the hosts file has :
s-usc1c-nss-262.firebaseio.com
on line 8419Similar to #1132 βΒ This domain is a general domain used by all Firebase platform customers. Firebase dynamically moves platform customers between subdomains to handle scaling. Here's an official explanation from a Firebase staff member on their forums (source) :
Q:
Staff Answer:
--
I believe that this week my service/app Cryptee, an open-source on-device encrypted, privacy advocating, productivity tools service, which relies on Firebase (for things like websockets as a part of our real-time productivity tools, as well as fallback for censorship circumvention), got moved onto the
s-usc1c-nss-262.firebaseio.com
server to handle the load. And now users of these hosts lists are having issues accessing our platform.Having this domain blocked also means, other Firebase clients are (or will be) impacted by this as well, some of which include : NYTimes Interactive, HackerNews API, occasionally Mozilla Firefox itself and companies like NPR News, Lyft, Shazam, and more according to some quick search on the internet.
I can at least speak on behalf of my platform, Cryptee, where we don't have any ads, tracking, or anything alike. Sadly, our customer support team (incl myself) are working overtime to handle this service-is-not-accessible situation right now. π
If possible, it would be great if you could remove
s-usc1c-nss-262.firebaseio.com
from the lists as soon as possible. (and for future, all domains following the samenss-###
pattern are a part of the same platform)If you know which specific service/company is using this domain for serving malicious content / ads, I'd be more than happy to take the lead and reach out to Firebase team to have it taken down altogether, so that others who use the cloud platform for good purposes can continue to do so.
Many thanks both βπ»