Jitbit Blog

That, plus: * Echarts is about the only dependency in our project that I can upgrade - and be sure it never breaks anything. It is so well-thought in that regard. Upgrading for 3.x to 5.x? Sure! "npm update" and everything just keeps working smoothly. That is so refreshing to see these days. Unbelievable. * It's both SSR-friendly and SPA-friendly. Being mostly vanilla-js, works seamlessly with both react/vue/apline AND with old-school rails/asp.net/php/whatever. Our app is pretty classic SSR (https://www.jitbit.com/) and I can construct my chart's JSON object on a server using some linq-queries and provide that to echarts. * ...OR I can give it a reactive object from vue-based SPA. Dun matter, it just works. * whenever we have to add some workarounds (like, showing hovering labels on a pie chart with a bold percentages or something) - I never have to dig into their sources. Almost anything has already been figured out. Easily googlable and "LLM-able".

I likeJitBit! Used it for a few years at my last role. https://www.jitbit.com/

I recommend trying out https://www.sql-ex.ru which has some good exercises which can trip up a lot of people. I have used quite a few questions from here as an interviewer. Going through it completely is a solid foundation for tackling SQL at work. As a baseline, if one can solve https://www.jitbit.com/news/181-jitbits-sql-interview-questions/ then you can be confident you can nail entry-mid level positions involving SQL.

Some people think that embedding a link to your site in a web product/plugin you distribute can lead to bad things, especially if it is not a nofollow link and your plugin is used by nefarious sites. http://www.jitbit.com/news/184-how-google-authorship-and-penguin-have-… has a bit about the Penguin algorithm and this effect.

Just to follow up on this: I did check with the team, and the message that Jitbit received ("Search results clicks for http://www.jitbit.com/xxxxxxxx/ have decreased significantly") pertains to the amount of clicks per day, not clickthrough. In other words, the message that Jitbit received--and that sparked this article--meant that Jitbit was getting less overall traffic from Google, not that clickthroughs had gone down. That's consistent with the site being affected by Penguin as well.

This reminded me of this internet folklore: https://www.jitbit.com/alexblog/249-now-thats-what-i-call-a-hacker/ There is also a recreation of the scripts at https://github.com/NARKOZ/hacker-scripts

Reminds me of this article https://www.jitbit.com/alexblog/249-now-thats-what-i-call-a-hacker/

And look at IEs market share until 2008.... https://www.jitbit.com/news/3304-browser-market-shares-1993-2019-anima…

Hard disks (multi-platter/multi head) can be refurbished in many cases by deactivating a head or a couple (a platter) of course re-labeling it to a lower capacity, I think it was a thing in non first-world markets. There was a recent thread post about a counterfeit external USB hard disk, though, JFYI: https://news.ycombinator.com/item?id=22019079 https://www.jitbit.com/alexblog/198-chinese-magical-hard-drive/

>> I should have bought a $45 1TB hard drive. He should be careful about hard drives too. Reminds me of this: https://www.jitbit.com/alexblog/198-chinese-magical-hard-drive/

Note that by not setting rel="noopener noreferrer" on the links you let the linked sites control the opener window (and of course see a detailed referrer header). https://www.jitbit.com/alexblog/256-targetblank---the-most-underestima… (This applies to more than just target="_blank")

Can I suggest rel="noreferrer noopener"? https://www.jitbit.com/alexblog/256-targetblank---the-most-underestima…

Some websites do use <base target="_blank"> to make links open in a new tab by default. However, this can create a vulnerability as the linked website now has a reference to your site through window.opener and can take the user away from your site: https://www.jitbit.com/alexblog/256-targetblank---the-most-underestima…

A quick Google for "outlook autoreply headers" gave me https://www.jitbit.com/maxblog/18-detecting-outlook-autoreplyout-of-of… -- a more comprehensive list of headers is available at https://github.com/jpmckinney/multi_mail/wiki/Detecting-autoresponders Will some things filter through this list? Undoubtedly, but I would be surprised if it's a significant percentage. Extremely high-volume lists probably need some more specific care, to be sure.

You may be talking about https://www.jitbit.com/alexblog/249-now-thats-what-i-call-a-hacker/ There's a repository with implementations of those scripts in multiple languages at https://github.com/NARKOZ/hacker-scripts

It could be some kind of 'target blank' attack, if you have Gmail open in one tab then open a link from a linkedin email onto their site, they have access to your gmail window and can probably get your contacts. Couple of examples explaining it better than I can: https://dev.to/ben/the-targetblank-vulnerability-by-example https://www.jitbit.com/alexblog/256-targetblank---the-most-underestima…

Wasn't this here a year ago in it's original form (from a russian website)? Edit: found it: https://www.jitbit.com/alexblog/249-now-thats-what-i-call-a-hacker/ . It was on Hacker News 275 days ago, but received only 4 comments. I guess I saw it on reddit.

Original (not-so-poorly written) source: https://www.jitbit.com/alexblog/249-now-thats-what-i-call-a-hacker/ Also linked to on the github page.

The original page is linked at the imgur page: https://www.jitbit.com/alexblog/249-now-thats-what-i-call-a-hacker/ Previous discussion: https://news.ycombinator.com/item?id=10605586 (48 points, 2 days ago, 0 comments)

I seriously doubt that, it should have been pretty easy to integrate other services besides G+. The truth is probably that authorship info sucks for many users, and this isn't news either https://www.jitbit.com/news/183-how-google-authorship-decreased-our-tr…

I do. I believe the person had the authorship stuff on their product pages. To me it looked like a blog post from the search result but by actually reading the headline you could see that it wasn't. Here is the article you are referencing: http://www.jitbit.com/news/183-how-google-authorship-decreased-our-tra…

For those that missed the original HN post: Original article: http://www.jitbit.com/news/183-how-google-authorship-decreased-our-tra… HN Comments: https://news.ycombinator.com/item?id=5792268 Matt Cutts' HN comment: https://news.ycombinator.com/item?id=5793803

> find a position that seems to involve a TON of manual work - automate all of it - and DO NOT TELL anyone This reminds me the article "Now That's What I Call a Hacker" [1], where a guy left behind his automation scripts when switched companies, which revealed some extreme scripts, like: > hangover.sh - another cron-job that is set to specific dates. Sends automated emails like "not feeling well/gonna work from home" etc. Adds a random "reason" from another predefined array of strings. Fires if there are no interactive sessions on the server at 8:45am. I'm putting this article and what you just said together. Now I think it's reasonable to believe there are a lot of IT professionals doing this, they are just hidden, because there is no reason to share this kind of works experience, as it makes sense in the competitive side of the industry. [1] https://www.jitbit.com/alexblog/249-now-thats-what-i-call-a-hacker/

This is interesting /** * Sites that link to theannoyingsite.com may specify `target='_blank'` to open the * link in a new window. For example, Messenger.com from Facebook does this. * However, that means that `window.opener` will be set, which allows us to redirect * that window. YES, WE CAN REDIRECT THE SITE THAT LINKED TO US. * Learn more here: https://www.jitbit.com/alexblog/256-targetblank---the-most-underestima… */ function attemptToTakeoverReferrerWindow () { if (isParentWindow && window.opener && !isParentSameOrigin()) { window.opener.location = `${window.location.origin}/?child=true` } } I checked in Chromium 70 and this only seems to work on the same origin - attempting to access `window.opener` cross-origin results in Uncaught DOMException: Blocked a frame with origin "https://example.com" from accessing a cross-origin frame The article linked in the code [0] and the MDN page for window.opener [1] mention the use of `rel="noopener"` to prevent `window.opener` from being set, but that it's not supported in all browsers - particularly Firefox, which needs `noreferrer`. I am sure CORS headers also play a role in protecting from this. OWASP calls this technique 'reverse tabnabbing' [2]. There's a demo [3] of the effect - you can manually inspect the first link and change the href to [4] and then click the link to test how cross origin requests work. [0]…

Most A/B testing will fail when you're testing the wrong elements. I have a challenge for you. The examples you list are "top" of the funnel tests: buttons for engagement, a homepage redesign. But when I go deeper into your funnel like your pricing grid page and cart checkout page, I see lots of tweaks that, in my experience, can drive the significant gains that you are looking for. I'm going to use this page as my starting point, by way of example: http://www.jitbit.com/hosted-helpdesk/purchase/ When I click order now on the "Startup" plan and get myself to the cart page here was my experience: a) The load time on click to page load for checkout was >3 seconds for me. You can get some idea of why here http://tools.pingdom.com/fpt/ or here http://www.webpagetest.org/ b) Your design changes drastically between those pages, breaking the user's flow and attention. 37signals products do a nice job of maintaining conformity between pricing grid to checkout as an example. c) You're treating a SAAS checkout like a product checkout - asking about quantity, list price, etc. What % of your users add multiple services to the cart? Can you keep this in more of a flow? d) You have no visible security certificate on the page at all, when in fact even the placement of your security certificate on checkout can make a drastic impact in conversion eg http://www.conversionvoodoo.com/blog/2010/07/proper-placement-of-trust… e) Yes,…