ushi

14 ms·

91.
by ushi 13y ago
> but why not just have the client do the pinging? That's exactly what i meant. Sorry if it was unclear. I accidentally switched proxy_send_timeout and proxy_read_timeout.
92.
by ushi 13y ago
The default proxy_send_timeout is 60s. If you rely on the information about connected clients (chat anyone?), it's way nicer to ping the server every 30s, than to set huge timeouts. If internet connection of the client breaks (mobile anyone
93.
by ushi 13y ago
> it's useful for when hosting statically. You can configure your webserver to add those headers, when hosting statically. There is no need to include it in all your pages. nginx: add_header Content-Security-Policy "...";
94.
by ushi 13y ago
When these coordinates are correct, i doubt he has something better to do: http://goo.gl/maps/hSz7r
95.
by ushi 13y ago
Ahaha, great headline... Seriously, the security of password protected systems are a disaster(, when combined with the average user). We should push static content generators like jekyll & co the reduce the surface, till somebody solves
96.
by ushi 14y ago
A part of your question is answered here: https://www.ubiquityservers.com/ddos-protection
97.
Show HN: My RSS/ATOM fetching/processing server (Go+Postgres)(github.com)
2 points by ushi 14y ago|0 comments
98.
New RC4 Attack(schneier.com)
3 points by ushi 14y ago|0 comments
99.
Guido Van Rossum Should Retire (and focus on python)(archlinux.me)
9 points by ushi 14y ago|0 comments
100.
by ushi 14y ago
Oh come on... >> Password is too long (maximum is 40 characters)
101.
by ushi 14y ago
https://github.com/postmodern/bundler-audit
102.
Read The Fine Manual(jasonwryan.com)
2 points by ushi 14y ago|0 comments
103.
[Show HN] CLI Password Manager - Time for a security review (github.com)
2 points by ushi 14y ago|0 comments
104.
by ushi 14y ago
Just search for '"foo_bar"' rather than 'foo_bar'.
105.
by ushi 14y ago
Are there any plans to make this available through the API?
106.
Dangers of Turbolinks(borisstaal.com)
4 points by ushi 14y ago|0 comments
107.
Mega.co and others hacked by omega(mega.co)
2 points by ushi 14y ago|0 comments
108.
by ushi 14y ago
When you are using the https:// page Chrome blocks the API calls, because it throws AJAX requests against the http:// API.
109.
by ushi 14y ago
What about a browser extension, where you enter some api key, before you can use it.
110.
Show HN: GitHub Search for your Chrome Omnibar(github.com)
2 points by ushi 14y ago|1 comments
111.
Russian Underground Offers Cybercrime Services at Dirt-Cheap Prices(wired.com)
1 points by ushi 14y ago|0 comments
112.
by ushi 14y ago
Paul Irish made something similar. A jQuery plugin that used localStorage to cache ajax responses. https://github.com/paulirish/jquery-ajax-localstorage-cache
113.
Google invites Chrome users to checkout Firefox and Opera. (whatbrowser.org)
2 points by ushi 14y ago|0 comments
114.
Mozilla Popcorn -- annotated, remixed and popped(youtube.com)
3 points by ushi 14y ago|0 comments
115.
by ushi 14y ago
Nice Work! Your https doesn't work for me because you make calls to the unsecured duckduckgo api and chrome refuses. You should use: https://api.duckduckgo.com
116.
A selection of 55 code {poems} as Book.(code-poems.com)
1 points by ushi 14y ago|0 comments
117.
by ushi 14y ago
KISS. IMO. KISS leads to a lightweight and fast system and moves much responsibility back to the user, which means that the user has to learn how the system works. I wouldn't be, were i am, without using stuff like Arch and FreeBSD. Know yo
118.
[video] Robert Neuwirth: The power of the informal economy(atropa.wurstcase.net)
1 points by ushi 14y ago|0 comments
119.
31 Linux distros in 31 days(webpath.net)
1 points by ushi 14y ago|0 comments
120.
by ushi 14y ago
here is a screenshot: http://imgur.com/suCbW

More ›