EOS tried to use on-chain Ricardian Contracts and pair that with upgradeable smart contracts in C++ with DPoS consensus so that intent-of-code could be enforced. That's pretty "real world" but most people feel it's not unstoppable enough.
Ethereum is pretty unstoppable, but unless you use a contract proxy, your contracts are immutable and bugs that can be exploited will be exploited.
Pokemon will enter the NFT digital collectibles space, and it would be absolute crazy if they don't already have a team working on it.
All of these collectors are making assumptions based on information other collectors have shared about "how many are known to exist" etc., whereas NFTs are provably scarce and they never get scuffed up.
Transaction fees for the Topps MLB cards on WAX, for example, are only taken during the sale when the sale occurs on a secondary Atomic Asset marketplace. There are no royalties to trade or transfer between accounts.
Our small team spends roughly $40-50k/mo at AWS. If you're just hosting a website with a SQL database (glorified LAMP stack), you're probably in it for the wrong reasons. Stick to a dedicated box or DigitalOcean etc.
AWS is like co-locating your hardware, and then the data center having 1000s of employees offering highly reliable services you can access from your infrastructure that lets you move WAY faster for things that are hard to do.
e.g. Discussion today was increasing log retention. 10 years ago I would have run the numbers, extended some SAN volumes, considered procuring more NetApp shelves, etc.
Today it's simply a cost question: is it worth it to us to store those logs for 10x longer? Sure? Ok, done.
As we head into the post-truth era, we already know videos are going to become far less trusted due to deep fake tech. Finding grains of truth through cryptography, like DKIM, is so refreshing that it hurts to think some people want to cripple it.
The Hunter Biden email is a good example.
I initially thought it was a garbage tabloid drop, but once I read Rob Graham's analysis, it felt very refreshing to have a real nugget of truth based on math. While the context of that content is up for debate, the truth was essentially undeniable (unless you subscribe to the 2016 private key being stolen).
I don't frequent /r/wsb, but the onus should not be on the SEC to clamp down on a community, it should be on the service the "significant young people" are using to execute satirical investment advice.
For example, if Robinhood wants to gamify everything, then advanced trading opportunities should be part of some built-in experience-based level up system. E.g. you can't trade options until you have made X classic trades, or after you've completed X days of simulated advanced trading.
Annoying for sure, but one benefit of this approach is due to forwarding. For the moment, let's assume you have a newsletter you enjoy. If you forward an instance of that newsletter to your friend, and they aren't expecting it, they might hit unsubscribe. With one click, they'll prevent you from receiving future newsletters.
I think the better approach is simply showing the "Intended for [email protected]" next to Unsubscribe, but I could see why they ask for your email.
We've had "Add List-Unsubscribe Header" on Trello for a long time, but for some reason I had it in my mind that there was a ~60 character limit.
I appreciate the post because after revisiting it, I think that info was gathered from a few-years-old blog discussing a specific limit in (maybe?) Gmail, but it sounds like it can be broken down into multiple lines.
UBI (in the U.S.) would be like printing more shares of a publicly-traded stock and giving all of the new stock to the employees of the company.
USD is the reserve currency, so foreign interests (or large corps) w/ stockpiles of USD will be the losers due to inflation.
Foreign interests can change which reserve currency they use at-will, so wouldn't this be like a direct-fee/dividend U.S. citizens (or any UBI-country citizens) could charge those that use the currency of the country but don't live there?
We spend ~$50k/mo on serverless infrastructure on AWS.
It hurts sometimes, given we were fully colocated about 4 years back, and I know how much hardware that could buy us every month.
However, with serverless infra we can pivot quickly.
Since we're still in the beta stage, with a few large, early access partnerships, and an unfinished roadmap, we don't know where the bottlenecks will be.
For example, we depended heavily on CloudSearch, until it sucked for our use case, so we shifted to Elasticsearch, and ran both clusters simultaneously until we were fully off of CS. If we were to do that on-prem, we'd have to order a lot more hardware (or squeeze in new ES cluster VMs across heavy utilization nodes).
With AWS, a few minutes to launch a new ES cluster, dev time to migrate the data, followed by a few clicks to kill the CloudSearch cluster.
Cloud = lower upfront, higher long term, but no ceiling.
On-prem = higher upfront, lower long term, but ceiling.
A few months before COVID-19 broke out, I started working with the founder of a platform called eTAP, which the founder first build about 20 years ago. We haven't begun the platform redesign yet, but it is fairly thorough platform for K-12 students who can benefit from an online supplement for math, science, language arts, and social studies. Parents can monitor progress, but don't need to be involved in lesson plans etc. as it's essentially ready to go.
Could you spoof the car to exit and continue thinking you were still on a freeway? A car being spoofed into thinking it was still on a freeway, while driving on city streets, might not prioritize certain rules when it approaches an intersection.
Every ticket I've ever created on the paid Developer support plan was within the "24 hour" and "12 hour" windows for guidance and system impaired issues. However, always always always at the far end of those windows.
Meaning if I had something I really needed help with, it was going to be a conversation for the following day.
I'm not really mad, we're just pre-release, and the number crunching to go from Developer adding 3% to cost vs. Business adding 10% to cost is too damn high. Our infra is about $10K/mo right now (pre-release), so we're talking $1000/mo for live chat and a shorter window vs. $250-300/mo we're paying right now.