please forgive my humble input, but wtf?
r/circlejerk ?
Show HN: This page will disappear in 10,000 views
31–40 of 95 posts
Re: Show HN: This page will disappear in 10,000 views
#32Re: Show HN: This page will disappear in 10,000 views
#33This is like Snapchat for the web, except it's too easy to take a screenshot of the content which means there's not much of a point to the view limit. You could make it difficult perhaps by requiring the user follow a path with their mouse, otherwise white noise appears. That way they cannot actually move their cursor to take a screenshot. Maybe do something else to occupy one of their other hands, such as pressing a…
You could improve it significantly by implementing something similar to this: http://www.donothingfor2minutes.com/ Any mouse movement or keypresses would blank the page and you'd have to reload it to see the contents again. Of course, there are probably ways to subvert this, but it would stop most people.
Most people would just take out their camera phone and take a snapshot, as they do on snapchat. Trying to make something like this secure from screenshots is absurd.
Re: Show HN: This page will disappear in 10,000 views
#34And it's gone :)
Meh, seems like it can be revived with another tweet.
Re: Show HN: This page will disappear in 10,000 views
#35Kinda feel like a jerk on this one. Wasn't really expecting to be able to nuke it so easily. ab -c 30 -n 3000 http://www.blinklink.me/b/4XIxfoeF4C0 Concurrency Level: 30 Time taken for tests: 93.802 seconds Complete requests: 3000 Failed requests: 2137 (Connect: 0, Receive: 0, Length: 2137, Exceptions: 0) Write errors: 0 Requests per second: 31.98 [#/sec] (mean) Time per request: 938.024 [ms] (mean) Time per request:…
What is ab?
apache bench
It lets you simulate hitting your web server to benchmark the speed. You can do cool things like test concurrent and sequential connections.
Re: Show HN: This page will disappear in 10,000 views
#36Am I the only one that finds this 'feature' utterly pointless?
Re: Show HN: This page will disappear in 10,000 views
#37I disagree with other posters, I think this is a great concept. It would be fantastic for brands to share promotional offers and voucher codes as people would have to tweet to revive access to the code therefore spreading the promo further.
Re: Show HN: This page will disappear in 10,000 views
#38I disagree with other posters, I think this is a great concept. It would be fantastic for brands to share promotional offers and voucher codes as people would have to tweet to revive access to the code therefore spreading the promo further.
How is this a good thing? You want users to visit a promo page, where they're forced to retweet the content before getting access? This sounds awfully familiar to those sites that ask you to share a referral link with 10 friends, or complete a survey before receiving a free gift that doesn't exist. Also reminds me of the days of browsing warez online. Click these three links to vote for us on Top 100 sites, then you'll get access to the file. They're just taking people hostage and encouraging spam on social networks.
Re: Show HN: This page will disappear in 10,000 views
#39This is like Snapchat for the web, except it's too easy to take a screenshot of the content which means there's not much of a point to the view limit. You could make it difficult perhaps by requiring the user follow a path with their mouse, otherwise white noise appears. That way they cannot actually move their cursor to take a screenshot. Maybe do something else to occupy one of their other hands, such as pressing a…
You could improve it significantly by implementing something similar to this: http://www.donothingfor2minutes.com/ Any mouse movement or keypresses would blank the page and you'd have to reload it to see the contents again. Of course, there are probably ways to subvert this, but it would stop most people.
I can still print screen undetected
Re: Show HN: This page will disappear in 10,000 views
#40Earlier quoted context omitted.
Don't use it for actual benchmarking though, it has lots of known problems. Use something like: https://github.com/wg/wrk
What sort of issues does ab have?
Well the best thing would be to try it yourself. I have found:
* ab has more results variation between runs
* ab will almost always report lower performance than wrk
* If you have two implementations being benchmarked, A and B and B is always faster than A. wrk will report a greater degree of performance separation between A and B.