1,143 karma · joined August 4, 2013
- Twitter w/out fake accounts.
- a marketplace that uses Facebook as a vehicle for engagement/promotion but which operates independently.
- Secure SMS for 2FA tokens
- Android w/out Play Services
- Schema-based email
- Stripe for the rest of the World
Do services like AWS S3 charge for 404's? If so, under brute force the monthly bill could get really big, no?
It is a very dangerous idea to seek a fairier distribution of wealth by taking it from the rich. If you doubt it go ask Venezuelans or Cubans if it worked out for them.
- When a Firebase ref changes I listen to the event in Nodejs and update a full text search index elsewhere.
- When a Firebase ref is created I send the appropriate transactional email/push/sms.
- Do data validations before pushing to Firebase.
So in general, I do things that cannot/should not be done on the client-side while still opting for serverless architectures.
PS: Parse.com was great in that it had server-side code that was run on events like object updated/created. The code was NodeJS. In sum, it had lambda-like functionality already built-in. But Parse.com closed shop. Not sure if any of its spin-offs are offering a good service at decent prices.
https://en.wikipedia.org/wiki/Tyranny_of_the_majority
To aggravate: many elections lately are win by tiny margins and with not all citizens casting a vote. Hence, the majority per se is not really setting the course of nations.
On a side note, I wonder why close results happen. I do not think it is an accident (some that I can remember now that are almost split in half: the popular vote in 2016 US elections, the yes/no vote for the Peace Treaty with FARC in Colombia, the 2016 presidential elections in Peru). Maybe there is no pattern either, but it seems odd that when facing an important decision, voters split in half. (my own conspiracy theory is that given the lack of grey area options - a raking effect as proposed by the OP - voters MUST pick a side and they are manipulated to veer in one direction by smart and sophisticated communications)
You'll do whatever if the right buttons are pushed.
For this reason, if Sailfish can trully run any Android app, I'd say they have a better chance.
Right.
Quoting:
There are many things users can and maybe should be concerned about: Hackers, providers, promoters, crooks, spooks, shareholders or maybe the person on the next seat in the bus. Do they want to prevent their data from being used for other purposes than communication itself? Maybe they want their messages to be tamper-evident, or perhaps they want plausible deniability or immunity against eavesdropping? What is the use of end-to-end encryption when there could be a key logger or a rootkit on their device, transmitting everything they do to a remote entity? Encouraging users to believe in a general sense that Signal makes their communication safe, will tend to promote a false sense of once-and-for-all security (regardless of the indisputable and substantial increase in end-to-end encryption). It is very important to remember that even though encryption will increase security, some information should not be stored in IT systems at all – and especially not if they are provided by a third party.
However this is no argument against the use of the Signal messenger or protocol itself. We instead want to think about the problems created or supported by OWS‘ promise of security.