> Firm Will Pay a Total of $38 Million in Penalties to Settle With Regulators
$38 million!?!? That's a expensive mistake for not submitting some paperwork that should be automated.
I'd like to see a list of international government agencies and what they can/do charge for penalty fines. I suspect that the United States SEC sets a high bar compared to some of the smaller fines I've seen elsewhere. GDPR appears to be one of the top contenders
Congrats Eric! I've been excited about this since your original announcement.
I'm hoping that you'll offer an index fund to make it for passive investors (and dollar cost averaging) to put more money in this exchange, with less effort, and push the wall street incentives toward longer term.
To expand on this idea, it would be cool if you could define a finite task you need (such as a user story) and exchange that for some other finite task that someone else needs. They work on your user story (in a skill they have) and you work on theirs (in a skill you have). Like bartering.
Right now, I see "Wanted: UX designer" but that doesn't tell me if they just need a menu bar, or an entire front-end for a mail client
You can actually mute the “microphone” feature (which is an electric disconnect internally, someone on HN mentioned before), and just use the smart speaker capabilities through the app, for playing music & setting smart home routines.
>> Morgan Stanley analysts pointed out in late March that the buying was running at eight times the pace seen in prior episodes of Fed purchasing under programs known as quantitative easing.
8x increase over QE is crazy. Is that 8x mortgage bonds or 8x bonds in general?
>> they send their staff of high powered attorneys to shop for an amenable forum and file the SLAPP lawsuit that your org can't possibly afford to defend in a court you've never heard about
It looks like you are correct, but only if you let them generate the password. If you define your own password, then you would have to share it via another channel-
>> While the Proton server will know the URL, it will never receive the password.
>> When creating a new shareable URL for a file, the web client will first confirm that a share directing to the file exists. The passphrase of this share must then be encrypted with the new password associated with the URL. This new password is either randomly generated by the ProtonDrive client, or is specified by the user.
>> In the case of randomly generated passwords, the user can choose whether they want to include it at the end of the URL, equivalent to sharing the content publicly. This section of the URL isn’t shared with Proton servers, making the password and the content inaccessible to Proton. Alternatively, the user can choose to share the password separately.
>> In the case of user-defined passwords, this option isn’t available and the password must always be communicated separately.