vincentchu

I have essentially no real knowledge about this topic, but I suppose some progress has been made by tightening the bounds for this constant?

Can somebody with more info chime in--- is this a huge, groundbreaking amount of progress?

A bit rusty on the math, but taking a quick gander at the Wikipedia page (https://en.wikipedia.org/wiki/De_Bruijn%E2%80%93Newman_const...):

"In brief, the Riemann hypothesis is equivalent to the conjecture that Λ ≤ 0."

This result seems to imply that the De Bruijn-Newman constant (Λ) is non-negative, i.e., >=0. Thus, were one able to prove that Λ=0, then one would have also shown the Riemann Conjecture to be true? Similarly, if one were to show Λ to be not equal to 0, then the Riemann Conjecture would be false.

Again, just a quick reading. Sure others who are better/smarter can chime in!

Update: Tao expands on this point in the bottom of his blog post.

Indeed! That's a great suggestion ...

Thanks for the feedback. I didn't mean to be shady (honest)!

The main problem is that the EFF doesn't have a publicly disclosed Eth address (they do accept BTC) so I just decided to support them by pledging to donate to them. Of course, nobody on the internet knows you're a dog, nor if you're honest ... :/

The fee does go towards hosting the campaign page. Also GiveHongBao doesn't charge for the deployment of the campaign contract--- that is paid out of my own account, so charging a small nominal fee felt fair to me.

I think an interesting point is to compare the fee to what GoFundMe and other similar sites are charging.

My motivation was mainly to make a competitive version that took advantage of Ethereum's native advantages:

- It's Global. You can use GiveHongBao anywhere in the world. You can't use GoFundMe unless you're in the western world

- It's direct. Your donations go straight into your wallet. You don't have to wait for a minimum donation size, nor do you have to wait for a certain time.

- It's cheaper. Ethereum transfers are a flat fee regardless of size (vs. credit card processing fees). I thought a fair thing to do would be to mirror this and charge only a flat fee (for hosting, etc..) then pass the savings on to campaign creators.

Hi all. The contract that distributes donations also transfers a fixed fee to my account. For instance, see: https://etherscan.io/tx/0xc27a96a1ed705b03604b91287d0e2cf76f...

The fee is flat and priced around a buck, mostly to help recoup some server costs, hosting costs, etc.. which I thnk is fair.

My main motivation was to make a cheaper version of GoFundMe or Patreon. Both of those sites charge a percentage on top of whatever credit card fees.

OP here. I started this project a few months ago, around early October. I wrote the meat of the solidity contract in a weekend or so, but the hardest part (of course) was writing all of the UI. That took another few weeks of intermittent nights and weekends.

Since then, I've just mostly been putting polish on it (testing, more refinements) mostly around making the app more responsive.

Happy to talk more about it-- it was a fun project that pulled together a lot of threads (Solidity, React, Web3, Infura, etc..)

That page will 404 since there's no campaign (campaigns are at addresses like: https://givehongbao.com/campaigns/support-jimmy-wales-of-wik...

If you want to create a campaign (free of charge) visit: https://givehongbao.com/create

Given that it took many minutes to generate the DAG, I'm wondering if your machine is a bit underpowered. You can make mining much easier by adjusting the difficulty parameter here (lower means faster mining): https://github.com/vincentchu/eth-private-net/blob/master/ge...

It was tuned to yield a block every 15 seconds or so on my laptop; may be slower or faster depending on how fast your machine is relative to mine.

Thanks! We were doing some deep technical dives into ethereum and cryptocurrencies here at Initialized Capital (where I work) and I was getting frustrated that I couldn't get all of the moving pieces together in one place.

This tool / tutorial was something I threw together to prove to myself that I understood everything, but then turned into something that I thought some other people might be interested in playing with.

testrpc is more of a backend for developing and running tests for solidity smart contracts (e.g., Truffle recommends it as a backend for testing).

My project is more focused on getting people to use the actual ethereum tooling (geth), and for them to learn what's going on under the hood.

The latest deep learning models are indeed quite large. For comparison, Inception clocks in at "only" 5M parameters, itself a 12x reduction over AlexNet (60M) and VGGNet (180M)! (source: https://arxiv.org/abs/1512.00567)

A further point is that even if the model has relatively few parameters, there are advantages to having more memory--- namely, you can do inference on larger batch sizes in one go.

Mine is similar, but uses drugs: http://bit.ly/2nW8GbR

The explanation is really pretty innocuous. We had an unaccounted-for edge case that cached paulphusion.de's pages under our root domain, posterous.com.

Like many software bugs, it was an edge case that we didn't foresee, but that happened extremely rarely. We've been running Varnish for the better part of a year, millions upon millions of requests and this was the first time something like this has ever happened.

Of course, none of that wipes the egg off of our face. ;)

No hacking here, just a simple misconfiguration in our Rails app. Nothing to see here, move along. ;)

Definitely graph memcached hit/miss ratios -- they're a good way to diagnose issues in your cache. However, I can think of a few instances where more logging is helpful:

1. Your cache server is shared between several different classes of objects. In this case, the overall memcache hit/miss ratios might mask issues occurring in one class of cached values.

2. You want to figure out how your cache will improve with a given change in cache size (i.e., simulate results ahead of time, as you mentioned).

Hey guys, thanks for the feedback. I've added in code that will also annotate the first point. See:

http://img.skitch.com/20100917-c7yqhxg74hq6tr97sfubshc441.pn...

There could be problems with truncation with "..." as well.

For instance, I can imagine the following trunactions:

"Anal...", "Ass...", etc.

I guess the problem really is the truncation. Hard to know what you're going to get.

It's not really a branding grab. The reason is pretty simple. We were contacted by Facebook because our stream stories were in violation of their terms of service, which forbid "Calls to action" in the body of the stream story. For instance, take a look at the old style stories we used to publish:

http://skitch.com/vincentchu/dne9u/facebook-vincent-chu

In this example, the "Read more on postmodern babbler" text was in violation and we were asked to remove it. So we did. But I still wanted people to have a "Read more" call to action somewhere, so I put it in the "Action links" area. Unfortunately that field is only 25 characters long. We've found that most people's blog titles will not fit into 25 characters. In fact, we've seen blogs where truncating the action link after 25 characters leads to some unfortunate text. For instance:

"Read more on Vince's Analytics Site" would become "Read more on Vince's Anal"

So in the interest of not creating bad looking text, we changed the text