Re:How to handle secrets on the command line
by kenty on Sunday June 13, 2021 @06:50AM
(#27491505)
About the cookie:
just install the extensions `CookieAutoDelete` and `I don't care about cookies`. No more cookie warnings, no more privacy problems.
About the article:
TL;DR: use a secrets file.
[ Parent
| on HN ]
Re:How to handle secrets on the command line
by klntsky on Sunday June 13, 2021 @07:04AM
(#27491555)
How is that different/better than uBlock with annoyances filters turned on?
Re:How to handle secrets on the command line
by joosters on Sunday June 13, 2021 @08:13AM
(#27491884)
Auto-deleting cookies means that you don’t need a filter list to block bad sites, every site will be wiped. There’s no chance that a missed site will sneak through.
The downside is that you will need to whitelist every site that you want to remember your login/settings for when revisiting them.
You can achieve that by just using incognito mode. Though the extension would surely be more flexible.
Still, I haven't used a browser extension in years, partly because of extensions like this that require access to all browsing data, even if they're open source like in this case (though the author of "I don't care about cookies" has a strange concept of distribution[1]). The inconvenience of wiping cookies and clicking through cookie consent forms is much more tolerable than allowing random extensions access to all my browsing data.
[1]: https://teddit.net/r/privacy/comments/bru6wd/p/eohtox3/
Re:How to handle secrets on the command line
by contravariant on Sunday June 13, 2021 @10:41AM
(#27493027)
Well uBlock can't block all cookie warnings, some of them are more than just cosmetic. And uBlock doesn't remove the cookies if any get through.