jakub_g

160 ms·

1621.
by jakub_g 14y ago
I don't like the solution on the page you linked. Try using it in Firefox with "zoom text only" enabled and do CTRL++ several times. The footer occupies half of the screen right now. Luckily there's Firebug / Aardvark to get rid of it.
1622.
by jakub_g 14y ago
+1 for "likes" in issues.
1623.
by jakub_g 14y ago
@wladimir Have a look at the Firefox userscript I wrote very recently: http://userscripts.org/scripts/show/153049 -- feedback welcome! Of course it doesn't eliminate the big initial fetch from the served, just collapses it once loaded to
1624.
by jakub_g 14y ago
English is a de-facto standard for programming - languages, docs, most of the tools are in English. Books come out in English long before being translated. This will not change any soon, and (I know it's controversial) but for the good of t
1625.
by jakub_g 14y ago
I select all the time, using either mouse or a keyboard. In addition to the mentioned problems with JS popups on click on NYTimes et al, there is another set of annoyances due to invasive keyboard shortcuts. I select text from kbd with SHIF
1626.
Show HN: GitHub code review assistant(userscripts.org)
3 points by jakub_g 14y ago|0 comments
1627.
by jakub_g 14y ago
The best thing to avoid a lot of style arguments is to have an automatic code formatter (on save, commit etc.) which takes care of indentations, spaces, braces and so on. Of course, someone needs to set up the options first, but then, life
1628.
by jakub_g 14y ago
For this kind of problems, I prefer userscripts solutions over bookmarklets as they don't require any intervention from my side -- they auto-load, which is great. This is the typical scenario for a userscripts -- predictable URL sets on whe
1629.
by jakub_g 14y ago
I've started thinking about all those banks [1] and other pages serving like/tweet buttons on the login page. Or pages including Google Analytics. If the described behaviors really take place, given the massive scale of deployment of Google
1630.
by jakub_g 14y ago
There are follow-up blog articles on the author's page. This one is also interesting: http://blog.dinaburg.org/2012/10/a-preview-of-bitsquatting-p... The original link was found at h-online.
1631.
by jakub_g 14y ago
TL;DR: every day, there are hundreds of wrong URL requests being done due to memory failures in the computers. Due to hardware problem, the computer can connect e.g. to microsmft.com instead of microsoft.com. The data gathered by the resear
1632.
Bitsquatting: DNS Hijacking without exploitation(dinaburg.org)
107 points by jakub_g 14y ago|35 comments
1633.
by jakub_g 14y ago
You need 2000 rep to do this, which is not so easy to gain, but certainly achievable for a highly determined person. However, what @wookietrader wrote applies -- each edit is marked with the person who has done it which solves the problem.
1634.
by jakub_g 14y ago
I was originally referring to fixing old typos (like spelling in documentation) that were in the repo forever. This, from what I understand this will take effect only if you introduced a typo recently and then you rebase so that the typo-co
1635.
by jakub_g 14y ago
Yep I wrote this with too much shortcuts. What I do is: git checkout typos, git rebase master, [fix typo & commit], git checkout master. This way I accumulate typo fixes in a separate branch, and merge a couple of them at once to master
1636.
by jakub_g 14y ago
FYI, in case you added reaaally a lot of stuff, and want to split it into smaller commits, it might be much more handy to do partial commits using Git GUI (select lines in the file & right click to have a popup menu with appropriate opt