The short answer to your question though is that the packets are sent over a secure tunnel.
177 karma · joined July 15, 2014
The short answer to your question though is that the packets are sent over a secure tunnel.
Cool that this article implements the cryptography primitives, though!
e: Funnily, like the article, I also stored some BTC in a wallet and challenged people to (manually) take/steal it. At the time it was worth $10 USD.. now it's worth $123 USD!
Is there anything you do that helps with this? I was using GApps and I don't think my domain name was too spammy (samlewis.me).
If they can get "good enough" results using Linux and running with technologies that the average developer is more likely to know, is it worth the investment in running a RTOS? Especially given running a RTOS will make any higher level app integration more difficult?
The benefit of running with Linux outweighs the risk of "lettuce on the floor", imo. Yes, there's probably overhead in terms of clock cycles, but there's also probably dramatically less overhead in terms of developer resources.. and when you're running off commodity hardware you can guess which overhead will cost more!
I've noticed that even for standalone graphical applications, it's becoming more and more common to use webapps - either served locally and accessed through a browser, or through something like electron.
The low amount effort to add an entry allows me to jot down thoughts, conversations etc easily which makes me actually do it.
Having it save as a plain .txt file is nice for versioning/backup as well.
Definitely makes me interested in trying something like this - does anyone know of any other games that have similar economy aspects?
# To send
gst-launch filesrc location=file.wav ! wavparse ! audioconvert ! audio/x-raw-int,channels=1,depth=16,width=16,rate=44100 ! rtpL16pay ! udpsink host=localhost port=1234
# To receive. You could also use something like VLC with "vlc rtp://localhost:1234" for this part.
gst-launch udpsrc port=1234 ! "application/x-rtp,media=(string)audio, clock-rate=(int)44100, width=16, height=16, encoding-name=(string)L16, encoding-params=(string)1, channels=(int)1, channel-positions=(int)1, payload=(int)96" ! rtpL16depay ! audioconvert ! alsasink sync=false
gstreamer gives fairly good control over tuning things like jitter buffers and sampling rates. That said, I've never had to use it on Windows so YMMV.I have my blog [0] setup so that all I need to do in order to publish a new article is add a markdown file to my GitHub pages source repo. Travis then builds the html and pushes it back to the GitHub pages repo.
You can easily add files and edit markdown on the GitHub web interface so I essentially use GitHub as a CRM. If you're interested, have a look at my GitHub Pages repo [1] and Travis CI build config [2].
[0] http://www.samlewis.me [1] https://github.com/samvrlewis/samvrlewis.github.io/tree/webs... [2] https://github.com/samvrlewis/samvrlewis.github.io/blob/webs...
For a bit more detail and if you're interested in this sort of thing, have a read of my blog article I wrote about the technical side of Bitcoin: http://www.samlewis.me/2017/06/a-peek-under-bitcoins-hood/
I suspect it was a design decision, yeah. If outputs could be spent multiple times then you'd need to traverse the chain of outputs backwards to see how much an output has left in it. Bitcoin's implementation is less complex and more elegant, imo.
I don't think there's any harm in people copying and pasting examples, it only becomes an issue if they start depositing money to either of the addresses that I listed the private keys for. I hope that's an obvious enough mistake not to make! Thanks for the feedback anyway, I'll keep an eye on those addresses and if they start getting mysterious deposits change the article to include more cryptographically secure keys.
So far it seems that these efficiency gains have been offset by growing demands in what software can do, making the industry continue to grow. I wonder if at some point in the future, these demands will stabilise and continued improvements in efficiency will necessitate a reduction in the workforce.
Will automation make a computer programmer's job disappear? No, probably not. But will it allow one person to do the job of ten? Maybe.
That said, the method of transaction signing would need to be reworked to be quantum safe. But not all Bitcoin would be able to be disappeared overnight.