I'm not seeing why they need a new cryptocurrency for this. If you grow Bitcoin (or any other existing cryptocurrency) to be "too big to fail", it would also have all these properties. Is starting from scratch with zero users easier?
1,067 karma · joined September 22, 2019
I'm not seeing why they need a new cryptocurrency for this. If you grow Bitcoin (or any other existing cryptocurrency) to be "too big to fail", it would also have all these properties. Is starting from scratch with zero users easier?
Having low friction payments on Facebook makes sense, it build value into the platform and Facebook can capture some of that. But can't they do that with an existing cryptocurrency?
It doesn't seem like Facebook will maintain full control of the currency due to the consensus algorithm. There is power and control if Facebook continues to control the fork of the code base that everyone uses, but presumably nodes could choose to switch away from Facebook's fork. So I'm not seeing "control a currency" as a long term benefit.
It makes sense that anyone running a Libra node would make money, but anyone else running a node would make similar profit.
The article mentions that a long term goal could be "act as a data broker and mediate consumers access to credit", although again, doesn't the decentralized nature permit any node from taking those steps? That doesn't seem to uniquely advantage Facebook.
As others mention, once a cryptocurrency is "too big to fail", regulators are locked out. Is Libra really an easier approach to getting a cryptocurrency to that point, versus adopting and accelerating the growth of an existing coin (like Bitcoin)?
Does Facebook just think they can build a better cryptocurrency? I don't doubt that they can hire good engineers, but with all the politics and marketing focus on the code now, development is probably getting stressful and chaotic.
Generally, going back to a known clean state should be easier, safer and relatively quick (DNS flip is fast, redeploy of old code is fast if your automation works well).
In some cases changes to your data may make rolling back cause even more problems. I've seen that happen and we were stuck doing a rapid hot fix for a bug, which was ugly. We did a lot more review to ensure we avoided breaking roll back. So I'd advise code review and developer education of that risk.
AWS pricing is certainly complex, and requires some research. Not user friendly.
> Ease of use → grandpa-friendly certified™
If I wasn't tech savvy and I stumbled into Puppy, I'd assume it was targeting non-tech savvy people based on that statement at the top of the homepage. Then I'd likely feel burned by "Linux" when it wasn't. There is a marketing problem there.
Although in that example, why is a mainstream user looking at puppy in the first place? So I think you're right, that's a cherry picked example.
I'm frustrated that CloudFormation ends up needing these customizations though, and that you need to leave the world of CloudFormation and self manage and deploy your own set of lambda functions to support your customizations. It feels like a hack.
I really strongly advise folks to look at Terraform instead of you can. While I've needed custom lambdas for CloudFormation, I haven't hit a similar limit for Terraform.
I think the above quote from the article is why Puppy was used.
Why is the front page for Puppy full of technical nit-picking about terminology? Why isn't it focused on getting the user to productivity faster and easier.
Or maybe to follow on to your point, why doesn't the Puppy home page clarify that install to disk isn't a goal. That info on the home page would have certainly helped the author more than the definition of a distribution.
https://netmarketshare.com/report.aspx?options=%7B%22filter%...
https://docs.microsoft.com/en-us/visualstudio/xaml-tools/des...
Remember, after the MVP you may end up pivoting in a new direction or scrapping the project, so I'd say what ever stack your team is most comfortable doing rapid development in is best.
Nice visuals on the website, but I don't think I understand.
> DNT Header Enabled? | 0.94 | 1.92 | True
I think this statement is misinformed. There are countries that have rules around protecting PII. WHOIS implementations have changed as a result, but I think these laws have carve outs that allow routers to function. The laws are more nuanced than this.
Examples:
ICANN adopted tiered access for gTLD registration information: https://www.icann.org/resources/pages/gtld-registration-data...
EU courts believe that IP addresses, even dynamic IP addresses, can indirectly identify a person: http://curia.europa.eu/juris/document/document.jsf?text=&doc...
GDPR, however has a carve out that I think permits use by internet routers. One legal justification is:
> Processing is necessary to satisfy a contract to which the data subject is a party.
If my ISP doesn't announce my IP address, then they can't connect me to the internet, which I pay them to do.
For EFI (per the screenshot) I wonder if they are looking to protect against the risk of an update that introduces an EFI vulnerability. Unless Apple is checking a certificate revocation list (or similar) then an attacker could apply that vulnerable update. Letting it expire sets a limit for how long it can be exploited. Just a guess.
Some of the links appear to be dead though: https://people.sc.fsu.edu/~jburkardt/data/byu/byu.html
There's a little bit of user blaming in that statement (not being critical, just thinking out loud). Dealing with the elderly and folks who are less familiar with tech is an interesting design space.
Does anyone know design patterns that specifically seek to improve the experience for non-tech savy elderly?
So not a fully offline method.
https://github.com/mozilla/addons-frontend/issues/2785#issue...