nonsens3
Joined 14 years ago
Karma
29
Submissions
24
Member since
Jan 16
https://powpark.com
View on Hacker NewsRecent submissions
Comment · 3 years ago
Hetzner randomly shuts down one of my servers every 2-3 months.
Comment · 6 years ago
Liquidation contracts and Arbitrage contracts do check the caller and would not allow to be executed by non-approved senders. This raises the bar, so that you can front run only contracts that you can implement and deploy.
If anyone could just replace an address and execute a profitable transaction by being first on existing contracts, surely miners would be doing it already, no?
Comment · 7 years ago
I stream live video (no audio) and watch how my dog chills at home while I am at work :) Sometimes I catch him on the sofa!
Comment · 7 years ago
Swarm documentation might not be perfect, but it is not outdated - https://swarm-guide.readthedocs.io
I believe the chapters about PSS, Swarm Feeds, ENS, Architecture, among others, are mostly up-to-date.
You can read about the incentivisation layer at https://swarm-gateways.net/bzz:/theswarm.eth/ethersphere/ora...
Currently incentivisation is not integrated or implemented in Swarm, so a user has no guarantees about what happens with their uploaded content. If the node hosting it disconnects from the network, it will be gone. The plans to address this are through the sw^3 protocols suite and/or erasure coding.
Regarding plain text - it doesn't really matter what bytes you store in Swarm - encryption is implemented and you can store non-encrypted or encrypted bytes, this has nothing to do with incentives for persistent storage.
We try to do outreach and answer community questions when possible, but the team is not big and this is currently done on a best-effort base, we could definitely improve on that front, I agree.
Comment · 7 years ago
I don't want to hijack the discussion from IPFS, but Swarm has good ideas with respect to dynamic content if you're interested how that might work in a decentralized setting, for example see Swarm Feeds presented here: https://www.youtube.com/watch?v=92PtA5vRMl8
Comment · 7 years ago
Swarm and IPFS together with Filecoin try to address the same problem - persistent data storage in a decentralised network.
Swarm is not at all "working already" - the incentivisation layer for nodes to store data for other users is not implemented and currently mostly theoretical and work-in-progress.
IPFS is more mature in comparison to Swarm, but the underlying architecture is rather different.
Comment · 10 years ago
Thanks a lot! I will try the `hyperbook` as a starting point.
Comment · 10 years ago
Thanks. This is also the paper I was referring to.
Comment · 10 years ago
Sorry for the offtopic, but have you ever used TLA+ to verify a non-trivial piece of production software? I recently found out about it, and was wondering if there are good public use-case details on it! I know Amazon has used it for some of their production systems, such as S3, and DynamoDB, but couldn't find many details.
Comment · 11 years ago
FWIW there is a http://taxime.to/ in Bulgaria, which has a reputation system and was embraced by existing taxi companies - you get a well-ranked driver that is licensed and insured, with overall quality much higher compared to random taxis in the country.
Comment · 12 years ago
Just wanted to say that I wrote the 2nd article you mentioned, and I fall more into the category of "engineer that just wants to play with things" rather than "run a mission-critical business", so take my article with a grain of salt. Thanks for the good summary!
Comment · 12 years ago
1) Testing a Dockerfile, then scp'd it to the server, doesn't guarantee that it will build successfully on the server. However if you build successfully an image and push it to a repository - it will definitely work. Based on this, you can decide which one works for your setup. If you are on a production setup, I would say that you should use tested images, instead of hoping that the Dockerfile will build correctly.
3) As far as I understand your problem is that both containers would be running their own nginx, and would have to take port 80 for example. If this is what you mean, you could just EXPOSE port 80 from within the container, and it will automatically be mapped to a random port like 43152. Both containers would be mapped to different random ports (for example 43152 and 43153). You could then install Hipache and route different domain names/sites to different containers, essentially having Hipache proxy in front your Docker containers setup.
EDIT: There is also a project called Shipyard, which is Docker management... what I described above is called "Applications" inside Shipyard.
[0] https://github.com/shipyard/shipyard [1] https://github.com/dotcloud/hipache
Comment · 12 years ago
Same problem here. Sideprojectors tries to solve this, but hasn't worked for me so far.
Comment · 12 years ago
Robert Sedgewick gives a very good analogy of a red-black tree to a 2-3 tree on his Coursera course (Algorithms, Part I) [0] - a bit different to what is discussed in Wikipedia, but very easy to understand and implement.