161–170 of 266 posts
Instagram does something similar if it detects that you are on mobile. A huge banner advertising their app is displayed, and the [x] in the top right corner is almost impossible to hit.
I loathe it so much I stopped using it entirely and just book marked my favourite podcasts like a filthy savage.
Earlier quoted context omitted.
What about if you want to A/B test on a non-logged-in user?
E-mail them and ask them nicely to volunteer for your research study. Agency's a bitch when someone else has it, eh?
Earlier quoted context omitted.
I like your idea, but it depends on what you see as "the opposite". There's already an opposite in existence: 1) Not complain about adblock (ie. silently allow it instead of moaning). 2) Simply don't use cookies. 3) Don't mention app (which is often just an Electron frontend anyway) in any way. 4) Allow the website to be used without signing up. These 4 examples used to be the default back in the early days of the WW…
I rather miss those early days. Web 1.0 is looked down on for its visual clutter (and definitely the hatred of image backgrounds and animated text was well-deserved), but Web 2.0 has just as much if not more clutter, and of a darker nature.
We should make a website that does everything in the opposite way: 1) Require adblock 2) Banner saying the website doesn't use cookies, which goes away if you mouseover 3) If you're on mobile, show a banner saying the website doesn't have an app 4) A signup form, but when you try to focus it, it turns into a banner saying "jk this website doesn't have signup"
My favorite part was how s-l-o-w-l-y the "How Can We Help?" dialog sank when I clicked Send to Bottom. I also appreciate how it would reappear and block the interface. But kind of disappointed it didn't instantly reappear if you moused over it. Or that it didn't randomly bounce for attention in my peripheral vision. And to the person out there thinking of making a front end framework based on this, just don't do it m…
I had this happen today, in the wild, after visiting a HN linked Wired article. A few seconds on the page, a banner appears, blocking about a quarter of the page. Close it, start reading the article. 30 seconds later, the original banner reappears, again blocking a quarter of the page, and I close it again. I continue reading, think I hit a "click to read more button", another click. Keep reading, maybe two thirds of…
Earlier quoted context omitted.
I like your idea, but it depends on what you see as "the opposite". There's already an opposite in existence: 1) Not complain about adblock (ie. silently allow it instead of moaning). 2) Simply don't use cookies. 3) Don't mention app (which is often just an Electron frontend anyway) in any way. 4) Allow the website to be used without signing up. These 4 examples used to be the default back in the early days of the WW…
I rather miss those early days. Web 1.0 is looked down on for its visual clutter (and definitely the hatred of image backgrounds and animated text was well-deserved), but Web 2.0 has just as much if not more clutter, and of a darker nature.
My favorite part was how s-l-o-w-l-y the "How Can We Help?" dialog sank when I clicked Send to Bottom. I also appreciate how it would reappear and block the interface. But kind of disappointed it didn't instantly reappear if you moused over it. Or that it didn't randomly bounce for attention in my peripheral vision. And to the person out there thinking of making a front end framework based on this, just don't do it m…
Intro to PeopleAggregator (turn your volume down first)
https://www.youtube.com/watch?v=oYTEf4amE74
Gnomedex 6.0: Marc Canter on People Aggregator (in which Marc explains why he doesn't have blue balls)
https://www.youtube.com/watch?v=c6Mesx1oRdo
https://techcrunch.com/2006/06/27/a-look-inside-peopleaggreg...
Earlier quoted context omitted.
maybe: 2) only works with cookies disabled for the site otherwise: 5) works better with Javascript disabled 6) works better in Firefox than Chrome 7) doesn't work if it can read your referer
> 5) works better with Javascript disabled Ironically, I find there's (broadly) two sorts of JS-enabled website: - completely broken without (often just a blank canvas) - works better without than with The most entertaining 'works better' example I've had is a site that gave me a free upgrade, because I was blocking client-side price manipulation. Google Maps however: block canvas fingerprinting, and it's Goodbye CPU…
Oh man, well played! Gave up at the user agreement, where you can't "accept" or dismiss until (presumably) you scroll to the bottom. The scrollbar is screwed up so that (1) wheeling is super slow and (2) you can't grab the elevator and drag it to the bottom of the shaft.
"Select all pictures with a bow" Then you have an actual bow. Like in archery. Next to a bowtie. Ok fine. "Select all pictures of glasses" Now you have a glass window. And glasses, as in spectacles. Holy crap, that triggers me.