205 karma · joined March 10, 2020
Except when there are none, you have to build it yourself.
no way facebook can be this tone deaf enough for this, just when you thought they couldn't go towards the nadir of desperation to continue to keep ruining their reputation.
do they even care?
OK, but so what?
Again the tech boffins would care about this enough to take action on this 'issue'.
You can always move your files away from Dropbox if you don't like it, I'm sure companies who are collecting information on you (name, email, browser, file_id) are doing this to improve the service that you've signed their TOS with.
> I love tech, but everyday I understand the libre hermit POV more.
Then don't use Dropbox or similar services then, it's that simple. There is always an SFTP/Rsync server waiting for you to upload your files on, or better yet for your usecase, an encrypted USB drive.
I'm stating a fact of this tech forum.
> Users don't even know that they are giving up privacy.
lol, Do you think the users care about privacy on Dropbox. The tech boffins might, but not the average user.
How have you been spied on as a Dropbox user? Can you do a better service than them? What alternative do you suggest that is in the same league as Dropbox?
how does the database fit into this?
how does the 'Jamstack' compare to Wordpress or it doesn't?
how does content get edited in the 'Jamstack' like Wordpress?
how is the 'Jamstack' 'mainstream'? compared to what?
why do I have to use Git to use the 'Jamstack'?
it doesn't make sense to spend a ton of money on a seat and not do anything. I am sure facebook has other motives than paying engineers to work on rust.
a regular sponsorship would have a been more enough in this case.
Say what you want, but the problem here is that you don't need to give board seats to those who have tons of cash, rather instead have them sponsor it, like how the R foundation has done.
Facebook essentially bought a board seat to drive and prioritise which features they want in the development of Rust.
The wolf eats the same grass as the sheep and gets praise for it.
I don't think DO's offerings are strong enough to compete with the big players long term, especially in production.
Seems like an exit for a later acquisition by a bigger company, like Slack with Salesforce.
The subscription apps on the App Store are suited for physical goods (coffee beans, etc) rather than digital (membership, gift subscription, saas, etc.) which is what is driving the subscription economy.
So building a digital membership platform on Shopify makes no sense, unless you consider sending shoes as a subscription to someone on a regular basis a 'digital membership'.
Tauri may be it, but the desktop SO needs this moment, I don't want to see 50 years on and Electron is still being used.
Before people are getting hyped around this, this is alpha software and not production ready.
If not, then no.
I would have expected this issue to be a solved problem too, and now we get extremely insecure Python 3 codebases as a result of this vuln.
So much for moving from Python 2 to 3, will now wait for Python 4.
I am genuinely curious why this is the case, am I missing something here?
Even my local grocer's website somehow needs Kubernetes skills all of a sudden, not kidding at all.
So we can say no deaths by comma, until proven otherwise.
Definitely not misleading.
I'm looking for straight answers, not going around points, but getting straight to them.
> ...it seems like the more reasonable thing to do is acknowledge that fact, rather than just ignore their point entirely.
The fact that Tesla and Uber has more deaths than Comma? That I can agree with.
This system is very powerful indeed.
> ...Tesla and Uber have killed people but Comma hasn't...
So no then.
This is the correct answer, thank you.