What's wrong with marking content NSFW? Its not censoring it, simply providing a warning to those who may be in a place where their screen is visible and that might not be appropriate.
Thanks for posting, turns out one of these was mine. I forgot that it existed. 1213 days of uptime, still running Debian Wheezy (don't worry, i'm bringing it up to date now)
That's odd because I've absolutely verified numerous Signal clients by entering a code, without granting access to my SMS (I use Google Voice so my SMS database is basically empty except for random spam from my shitty carrier)
I used to use something called UTM Mangler that would replace the referral links with shock sites. I felt that was much better than simply removing them.
I don't understand how any of those are remotely related to whois being removed. It's not like it represented anyone that could feasibly be sued before, just a whoisguard service, usually
You've linked that thread a couple of times here, never really elaborating on the nature of your concerns, nor do you elaborate on the specific nature of your concerns in the ticket. Have you considered elaborating on the nature of your concerns? Is there a specific vulnerability in chromium you feel could be exploited here?
It'll be interesting to see how this works, given that the Signal Desktop client's main page (background.html) includes a CSP that restricts it from running inline or external scripts. It can only run JS that's already in the Signal Desktop package (in theory).
The fact that this isn't being described as an issue with CSPs or electron makes me wonder how it could possibly work.
These look really nifty. I'm hoping GitLab will add similar. I particularly like that the build can be failed due to a specific line. I've noticed that all of the CI output can be confusing for some, and it becomes difficult to suss out the specific error messages amid all the other output.
The only API they don't support that I know of that somewhat bothers me is that notifications can't have buttons or actions. The bugzilla issue[0] has been sitting without much updates for a while.
Native apps have led to slow, bloatware-, spyware-, and malware-infested mobile devices. The browser is a much better sandbox, giving much less permissions to the untrusted code.