Bug Bites
-
@boomzilla said in Bug Bites:
@Arantor a question you could ask a CommunityServer dev if you could find one.
I've got a long list of questions as to why their system isn't sem
aniotically compatible with Lysenkoism to get through first, tho.
-
@boomzilla said in Bug Bites:
@Arantor a question you could ask a CommunityServer dev if you could find one.
I've got a long list of questions as to why their system isn't sem
aniotically compatible with Lysenkoism to get through first, tho.Sounds like a good use of all y'all's time.
-
logout, a non idempotent action
Does it check, and fail, to log out if not logged in first?
Well, kinda exactly not - it says
Forbidden
but leaves me logged in.
-
@Gribnit No, that's a wrong interpretation.
Version 2002
is encoded withyymm
, so it stands for Februaray 2020.
-
@BernieTheBernie said in Bug Bites:
@Gribnit No, that's a wrong interpretation.
Version 2002
is encoded withyymm
, so it stands for Februaray 2020.Oh, "mm".
-
The G in my avatar is so much smaller in thread than in topics list.
-
@Gustav Letter avatars are generated in the browser (unlike in discourse, which has a CDN to serve them as images).
-
@PleegWat and for some reason in the CSS the font size on the topic list is 2.875rem but in a topic it's 1.5rem
-
@PleegWat We could theoretically have done something different, like generating the letter avatar images once per user, then storing them like normal avatars, but that would be far too simple and logical
-
@PleegWat We could theoretically have done something different, like generating the letter avatar images once per user, then storing them like normal avatars, but that would be far too simple and logical
Doesn't sound very civilised.
-
@loopback0 said in Bug Bites:
the topic list is 2.875rem but in a topic it's 1.5rem
Be careful how much time you spend on TDWTF, especially looking at the topic list. The human eye shouldn't be exposed to more than 1500 rem/year.
-
-
@PleegWat We could theoretically have done something different, like generating the letter avatar images once per user, then storing them like normal avatars, but that would be far too simple and logical
-
@HardwareGeek said in Bug Bites:
@loopback0 said in Bug Bites:
the topic list is 2.875rem but in a topic it's 1.5rem
Be careful how much time you spend on TDWTF, especially looking at the topic list. The human eye shouldn't be exposed to more than 1500 rem/year.
This much exposure can make you lose your religion.
-
@HardwareGeek said in Bug Bites:
@loopback0 said in Bug Bites:
the topic list is 2.875rem but in a topic it's 1.5rem
Be careful how much time you spend on TDWTF, especially looking at the topic list. The human eye shouldn't be exposed to more than 1500 rem/year.
This much exposure can make you lose your religion.
Did you think you thought you saw them try? Are you in a corner? Maybe in a spot light? Did you say too much?
-
-
@topspin that's one creative emoji. I like it!
-
@HardwareGeek said in Bug Bites:
@loopback0 said in Bug Bites:
the topic list is 2.875rem but in a topic it's 1.5rem
Be careful how much time you spend on TDWTF, especially looking at the topic list. The human eye shouldn't be exposed to more than 1500 rem/year.
This much exposure can make you lose your religion.
At 3000 rem, spotlighting is likely.
-
In another installment of "I thought everybody in America has an iPhone, why does nothing work on mobile": If you open chat on mobile and typed more than 2 messages so the screen scrolls, you literally can't see the text box while typing.
(No screenshot for obvious reasons.)
-
-
@Tsaukpaetra that isn’t even NodeBB!
-
@topspin my experience on this subject is that unless someone in the dev team explicitly has an iPhone, iPhone support is at best hopeful.
Not because the iPhone does anything particularly weird (except be behind current Chrome for support of more out-there features), but because if no-one in dev has an iPhone, it'll be tested on one person's Android that will be customised like no other and of course be in no way representative. And no-one outside the dev environment would test on their own device because if they're at work, they're using work laptops to look things up/try things.
Even a team of hipsters all using MacBooks is no guarantee that the iPhone support will be any good.
-
a team of hipsters all using MacBooks is
noa guarantee thatthe iPhone supportnothing will be any good.for
-
@Tsaukpaetra that isn’t even NodeBB!
I've demonstrated screenshots multiple times of .
Thought I'd mix it up.
You know, for science. You monster.
-
@HardwareGeek I'll have you know that I turn out finest quality PHP from my work MacBook!
-
@topspin my experience on this subject is that unless someone in the dev team explicitly has an iPhone, iPhone support is at best hopeful.
That’s why my post said:
I thought everybody in America has an iPhone
-
@topspin No, no, the regular users have iPhones, the developers seem to think themselves above such devices.
-
@topspin No, no, the regular users have iPhones, the developers seem to think themselves above such devices.
Can't imagine why.... ↩
-
@Tsaukpaetra said in Bug Bites:
@topspin No, no, the regular users have iPhones, the developers seem to think themselves above such devices.
Can't imagine why.... ↩
They don't have iPhones because they make poor decisions. That's also why they develop using Node.
-
-
@loopback0 said in Bug Bites:
they make poor decisions
And yet you don't hear about programmers working two jobs to feed their family
-
@loopback0 said in Bug Bites:
they make poor decisions
And yet you don't hear about programmers working two jobs to feed their family
Programmers barely work one job
-
-
@HardwareGeek And some programmers are working hard, while they are actually hardly working...
-
In another installment of "I thought everybody in America has an iPhone, why does nothing work on mobile": If you open chat on mobile and typed more than 2 messages so the screen scrolls, you literally can't see the text box while typing.
(No screenshot for obvious reasons.)Bah. NodeBB is Canuckistanian.
-
¿Üñíčōðçę?