1,143 karma · joined August 4, 2013
Why was the bicycle, a very simple machine, invented 100 years after the steam engine, a very complex one? My theory: the idea of auto-motion had to be invented first. I imagine, the inventor of the bicycle must have observed a moving train and though: hey! like those levers, my legs could move a wheel as well. Eureka!
The blockchain is a very, very powerful idea, the application as decentralized, untraceable currency is powerful as well, even though we clearly understand the pitfalls. But the idea is already there, with real life applications, with many advantages.
For this particular case, I think we better fix/improve infosec rather than hunt down cryptos.
You are correct: crypto enables crime. But the solution is to fight hacking, not crypto currencies.
Context: I live in a very corrupted country.
Rich or not, what is the right thing to do?
Thanks for the hard work boys and girls! You set an example of how the world should work.
Thanks!
Thanks!
Thanks!
On Twitter, I try hard do a better job moderating content by carefully selecting who to follow; however, much noise is unavoidable. (Twitter needs to rethink itself)
On the other door, this door, I ALWAYS end up in the right spots. This is the best site on the web, no doubt. Here I discover, I learn, I get inspired. I get downvoted too :)
Thanks mods!
In order to run such stacks we need to devote a couple of GB's of RAM for the OS and browser. Not a bad deal if you compare cost to benefits.
Can I do all this with Stacker? Merely using a couple of Google Sheets as my back-end DB?
I wrote something similar to BaseDash ages ago, I called it dAgent (for database agent). I had it running for many different clients from all sorts of trades (I do custom development). The GUI built itself from reading the DB schema.
My initial motivation was to cut dev time since dAgent would automate the coding of CRUD interfaces. However, the use of dAgent in production ended up being quite limited: maybe only used to edit catalog data (i.e. add a city to the cities table). The reason for this limited usage is no mystery: one can easily break things. In particular non-IT users can break things.
Allow me to use an example. You have a CRM with a customers table. On that table there is a field called status. For that field, dAgent would load a select input using the related table statuses, there was no risk to break integrity. However, in the business logic of this CRM, changing the status of a customer is the result of running a process. That process not only sets the status of a customer to a new value, but also writes a history log, sends email notifications and perhaps triggers an invoicing process.
Now, imagine a non-IT user changing the status field of a customer using a tool such as BaseDash. Now you have a customer in status active who is able to login to your paid SAAS but has never being invoiced.
Many such nightmares can happen when users can directly edit a DB.
For this reason, in production, dAgent features where limited to CRUDing simple catalog tables. It did help, but was not the silver bullet I had hoped for. On the other hand, IT users would never adopt dAgent since the DB engine provided a much more robust and feature-rich admin GUI. I was not in the business of competing with PHPMyAdmin, so I eventually dropped the project.
https://magic.wizards.com/en/articles/archive/news/depiction...
There are many racial issues at WotC that need fixing, many.
Why using res-sellers, like carriers use re-sellers to sell SMS integration? Distribution and fair-use control. First, companies like Twilio are the natural partners to sell one more channel to customers that already integrate to SMS. Second, partners will help enforce and control anti-spam efforts. If opening Whatsapp API turns it into a spam jungle like email or sms, it will certainly lose its appeal and users will start switching to the next new spam-free chat app.