A JavaScript browser library fails due to an adblocker blacklisting 'beacon.js'
Remove hint on beacon.js as it's apparently a bad name · ntzwrk/beacon@17c2042

    This repository has been archived by the owner on Nov 14, 2023. It is now read-only.
  
  
  Commit


Permalink



  
    
        
          Remove hint on beacon.js as it's apparently a bad name
        
    

    Browse filesBrowse the repository at this point in the history
  

    A few days ago I noticed some weird behaviour in the beacon.js
repository. I wasn't able to view repository statistics, merge pull
requests and some other minor bugs. That was especially strange because
I created two repositories (beacon and beacon.js) that I used exactly
the same way. So I contacted the support and stated that there are some
strange things going on in this repository.

And as always with technical issues: "Hm, that's not reproducible on our
side". I tried with different browsers etc, still problems. After some
back and forth I figured out that the only similarity was that an
adblocker is installed (never thought of this being a problem).
Apparently the EasyPrivacy blocklist has an entry for URLs that contain
"/beacon.js" and therefore blocked some internal requests on GitHub from
loading additional information.

So the moral of this commit message is: Yes, objectively bad names
exist. Think about your naming, and don't forget your adblocker.
Unflexible blocklists may block a few more things as they are supposed
to.

Fortunately I thought about merging these both repositories before. So
beacon.js is now gone, everything will take place in this repository
from now on.

Thanks @vbrandl for helping me to resolve this :)

  
  
    
      
      
        Loading branch information
      
    



  



  


  
    
        


