little-rat VS murder

Great idea! We need a lot more visibility into what extensions are doing. I made little-rat [1] last year, to detect network calls coming from other extensions. Love to see more tools like yours!

[1] https://github.com/dnakov/little-rat

It says 1.0 in the extensions manager, but it was downloaded fresh this evening by clicking on the 'ZIP' link in your readme.md on here:

https://github.com/dnakov/little-rat/tree/main

2: https://github.com/dnakov/little-rat

I recently installed the Little Rat chrome extension, which I found here on HackerNews.

https://github.com/dnakov/little-rat

And what I found is that the Midnight Lizard chrome extension is monitoring my browsing-- sending home screenshots.

You can see examples here: https://ibb.co/JQvgt3p

Apparently my browsing data is being ingested by a company called "Mark Monitor Inc." (based on WhoIs search for the domain the data is sent to -- https://www.whois.com/whois/ytimg.com )

Nifty - but please do this more carefully:

https://github.com/dnakov/little-rat/blob/main/popup.js#L36

I do not want to have to worry about whether another extension can inject xss into yours with a crafted request/id/name.

When a user submits a tweet or post URL: https://twitter.com//status/

You can send a Tweet URL that looks something like this to the bot: https://twitter.com//status/

4. X

I went to https://twitter.com/ and only got the login page. You can see individual posts without an account, but most other read-only functionality is hidden behind the login wall.

It is this ublock origin custom rules

    news.ycombinator.com##tr.athing:has(a[href^="https://twitter.com"]) + tr + tr.spacer

I don’t know that the rename is going to stick. The logo is still an X in blackboard bold, but https://x.com/ links now redirect to https://twitter.com/.

Case in point.