535 karma · joined January 14, 2015
In the long run I think that continuous training will be obvious with new models rolled out on a very high frequency if not continuously.
All programmers will become translators from product vision to architecture implementation via guided code review. Eventually this gap will also be closed. Product will say: Make a website that aggregates powerlifting meet dates and keeps them up to date. Deploy it. Use my card on file. Don't spend more than $100/month. The AI will execute the plan.
Programmers will come in when product can't figure out what's wrong with the system.
Also worth mentioning, what is illegal strongly depends on jurisdiction and can sometimes be moral despite their legal status.
> the gateway is in full control and can inspect and tamper with the data as much as it likes. And there is no way for the client to know or detect if it is happening.
Regarding data tampering;
IPFS uses content based addressing, the point is that the client _can_ know by computing a message digest of the incoming data. The verification is fast and cheap.
Discussion with the "Bitcoin Beach" people https://stephanlivera.com/episode/279/
> The protocol serializes an HTTP request and wraps it inside a Bitcoin OP_RETURN output script. This is then signed with a Bitcoin wallet's identity private key and included as another output script in the transaction. The resulting Bitcoin transaction is sent to a destination Vapor API endpoint over HTTP.
> A Vapor endpoint only accepts HTTP POST requests with a raw bitcoin transaction as payload. The endpoint parses the transaction to extract out authentication information, validates the signature, and then forwards the extracted HTTP request to relevant API endpoints.
I actually think this is probably better suited as a library, then there is no need for any intermediary calls that will inevitably increase latency. Also, would the vapor server somehow send the information about the public key on to the destination server?
I think I understand the concept as something like "login with your bitcoin identity" but I'm struggling to understand practically how what you're envisioning is meant to work.
I actually think this could be made far more generic as "login with public key identity" for any crypto scheme, Ethereum or just about anything that is not mimblewimble and/or hyper privacy focused should work similarly.
[1] https://en.wikipedia.org/wiki/Arizona_Stock_Exchange [2] http://reports-archive.adm.cs.cmu.edu/anon/2012/CMU-CS-12-12... [3] https://medium.com/bollinger-investment-group/constant-funct...