octavn's comments

A webcam & microphone JS tester library that you can put in front of your WebRTC or MediaRecorder web app to diagnose any possible issues (the presence of getUserMedia, secure context, required devices, policies blocking device access, supported resolutions, etc.). It also primes your users’ OS/browser permissions before they get to the real app.

https://github.com/addpipe/webcam-tester

Live demo @ https://addpipe.com/webcam-tester/

System audio (i.e. Zoom calls) can be captured only on Chromium browsers on Windows and ChromeOS when sharing the entire screen; tab audio has wider OS support; Safari and Firefox do not support system or tab audio capture https://addpipe.com/docs/recording-client/screen-recording/#...

The MDN support table does not differentiate in this regard. (le: it actually does if you click to see the implementation notes)

That seems overkill. @levelsio ran his $1M business on "FTP" https://twitter.com/levelsio/status/1327451757975375874

I remember the tool. Saved me many times during my heavy Flash development years!

It's not free even if you put in just your time. In a startup, everything competes for your time. You could spend it on your product or other growth channels.

Actually, under the GDPR, as a general rule, you can't just keep personal data on your servers forever so GDPR might be involved but for personal data cleanup reasons/requirements.

Kudos to GDPR obliging companies to allow users to delete their personal data.

You can find "slim" webcam privacy covers on Amazon. Since they can slide it they're a better solution than tape.

1st world problem

I used to live in Romania where hospitals are full of deadly bacteria, doctors are corrupt, nurses are corrupt. There's a shortage of equipment, vaccines, cancer treatment, important medicine, you name it. There is no place in the country to treat a seriously burned man, they all die. Obviously, lifespan here is shorter than in the US by about 4-5 years.

Revolut allows you to generate "virtual" credit cards which are just disposable credit card numbers linked to your account. You can spun one for every major online service you use (Netflix, Amazon, etc.) in case it gets hacked or for any transaction you're making on a less trusted site.

No you don't.

AS per the GDPR I see no possible solution for the “reasonable measure to verify the identity of a data subject” against an IPv4 IP and thus to reliably act on IPv4 related data subject access/deletion requests.

Also per the GDPR, providing data to the wrong person could “affect the rights and freedoms of others” in which case you shouldn’t provide the data.

Yes they are.

I wouldn’t worry about individuals requesting access or deletion of the Apache logs concerning a certain IP as I see no possible solution for the “reasonable measure to verify the identity of a data subject” against an IPv4 IP and, as per the GDPR, providing data to the wrong person could “affect the rights and freedoms of others” in which case you shouldn’t provide the data.

>Saving ip adresses in log files can be fully complaint IF you only use them for legal reasons (sue an attacker, ...), have severe access restrictions on the files, delete them as fast as possible and get consent from the user prior to saving the logs.

You do not need consent for saving the IP, user agent and URL (including GET values) in Apache logs because, as someone said above, you have a "legitimate interest to combat fraud and maintain information security".

Legitimate interest and consent are only 2 of the 6 legal bases under which you can collect and store (process) personal data. Art. 6 contains all 6 https://gdpr-info.eu/art-6-gdpr/ .

Wow, that was fast. Thanks DO :)! Hope you can make the other changes too in the future. Change does not break extension.

Similarly their new "Monitoring BETA" product/section is just a confusing name for Alerts.

That's pretty much how it works in bigger companies.

I actually did open a ticket.

Their support suggested I post on their UserVoice ( http://do.co/uservoice ) which I did and sent them the links. They've then passed the links "along to our control panel team so that they are aware".

I work in a similar software company and I know how much time it takes from an idea coming through to support > product managers > UI > implementation > QA > rolling out to production so I just built the extension myself.

June 2007: iPhone is released July 2008: iPhone OS 2.0 is released September 2008: Android 1.0 is released

This is part of a bigger company wide strategy to offer software updates for free for their products, a strategy they pioneered with iOs.

There's also a huge difference in what each update adds when compared to 8.1 . Where 8.1 tries to fix all the initial issues with W8 (missing start button anyone?), Maverick adds serious new features (1+ hour of battery, compressed RAM).

The free iWork suite is a direct attack to MSFT Office. Giving it away for free will pay long term in decreasing market share for Office. Office H&O is $220. Buy a Mac/iPhone/iPad and you get that for free.