11–20 of 247 posts
Hey look it's Mr "it's 2020 but I still don't give a shit about mobile users". Why would anyone want to alienate a substantial amount of users especially if they're serving ads on their blog?
> Hey look it's Mr "it's 2020 but I still don't give a shit about mobile users". Nobody owes you their site behaving a certain way on your phone.
Hey look it's Mr "it's 2020 but I still don't give a shit about mobile users". Why would anyone want to alienate a substantial amount of users especially if they're serving ads on their blog?
> Hey look it's Mr "it's 2020 but I still don't give a shit about mobile users". Nobody owes you their site behaving a certain way on your phone.
Not a good idea to use 9 to 11 digit long IDs with no password requirement by default; they should have used at least 128-bit random ids, i.e. 21 character long base64-encoded strings.
Yeah but then it sucks for people calling in to have to punch in a 21+ character long meeting ID
Example: tel://18005551212,,#
Not a good idea to use 9 to 11 digit long IDs with no password requirement by default; they should have used at least 128-bit random ids, i.e. 21 character long base64-encoded strings.
How hard is this for them to fix?
Hey look it's Mr "it's 2020 but I still don't give a shit about mobile users". Why would anyone want to alienate a substantial amount of users especially if they're serving ads on their blog?
FWIW I loaded the article on my Pixel 2 and it looks fine. In the Chrome browser if you double tap on the article text it zooms in to the article.
Not a good idea to use 9 to 11 digit long IDs with no password requirement by default; they should have used at least 128-bit random ids, i.e. 21 character long base64-encoded strings.
Yeah but then it sucks for people calling in to have to punch in a 21+ character long meeting ID
I may be out of touch with the average biz-guy, but how many people are realistically calling in manually, over traditional phone-lines these days?
Is it really a significant percentage?
Not a good idea to use 9 to 11 digit long IDs with no password requirement by default; they should have used at least 128-bit random ids, i.e. 21 character long base64-encoded strings.
Yeah but then it sucks for people calling in to have to punch in a 21+ character long meeting ID
Earlier quoted context omitted.
> Hey look it's Mr "it's 2020 but I still don't give a shit about mobile users". Nobody owes you their site behaving a certain way on your phone.
It's not really about entitlement. He's the one benefiting from people consuming his content, why not make it more accessible? All at the cost of some CSS rules.
The tone of your opening sentence fooled me then.
> why not make it more accessible?
Maybe because he doesn't give a shit about mobile users.
Not a good idea to use 9 to 11 digit long IDs with no password requirement by default; they should have used at least 128-bit random ids, i.e. 21 character long base64-encoded strings.