This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly"
-
Mentions are cut off if browser top bar is visible.
Page change is bar is badly colored, and inconsistent.
Above has more pages, below does not.
If one is close to the middle of a thread there may be an ellipsis to the left of the last page number. But it's quite inconsistent.
-
Where are you people coming from with your tiny screen phones
-
@Tsaukpaetra tiny? That's 1080x1920.
-
This thread was not titled "Through A Mobile CSS, Darkly"
FLAGGED FOR IMMEDIATE MOD CLOSURE!
-
@Lorne-Kates why close it? they can just rename it.
-
@anotherusername said in Darkly mobile css:
@Lorne-Kates why close it? they can just rename it.
Closing effort << Renaming effort
These arebolded text**** TDWTF mods...
-
@Lorne-Kates well, now that you made the tremendous effort to type it, they could at least copy-and-paste it.
-
@anotherusername said in Darkly mobile css:
@Lorne-Kates well, now that you made the tremendous effort to type it, they could at least copy-and-paste it.
And risk exposing a NodeBB "we fucked up re-implementing the clipboard" bug? Too much effort.
-
-
And occasionally looks like this.
It's not wrong per se, but it could be better.
-
@anotherusername said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
tiny? That's 1080x1920.
Did I ask for native resolution? No? Well then.
-
@anotherusername said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
tiny? That's 1080x1920.
Tiny != low-res.
-
-
@blakeyrat said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
@anotherusername said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
tiny? That's 1080x1920.
Tiny != low-res.
Tiny should directly relate to how much information can be fit on the screen, and the number of pixels is the single largest factor involved in that.
You remind me of this guy I work with. His computer screen is a big-ass TV, but it's an ancient piece of crap with fewer pixels than a 1024x768 laptop.
-
@anotherusername said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
Tiny should directly relate to how much information can be fit on the screen, and the number of pixels is the single largest factor involved in that.
Except it's not, because if your screen is 7" and you're drawing font size 12 with no zoom, ain't nobody able to read that.
That screen could fit a shitload more information on it, but without a big magnifying glass no human being's gonna be able to read it, so what would be the point?
-
@blakeyrat I'll just leave this here:
And now let us all collectively wonder why in the fuck would you need that.
-
@Onyx ? Leave it here why? Not sure what you're trying to communicate with me.
-
@blakeyrat If you read the one sentence that appears you'd see that some moron thought that a 4k resolution on a handheld device is actually something we really need in our lives.
Also, it's for anyone coming along, I just replied to your post since it's thematically relevant.
-
@Onyx said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
And now let us all collectively wonder why in the fuck would you need that.
in case you're viewing the screen from half a millimetre away
-
@blakeyrat did you throw a dart at your magic dartboard and it told you what the screen size of his device is? The PNG metadata says his screen is 96 DPI, which is useless because that's undoubtedly wrong (unless we think he has a 23" phablet). And the only other bit of useful information is the resolution, which is 1920x1080.
-
@Onyx said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
If you read the one sentence that appears you'd see that some moron thought that a 4k resolution on a handheld device is actually something we really need in our lives.
More resolution = better. That said, I wouldn't buy a phone merely for that reason, but ideally every screen every where should be like 473 billion DPI, so.
@anotherusername said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
@blakeyrat did you throw a dart at your magic dartboard and it told you what the screen size of his device is?
@anotherusername said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
@Tsaukpaetra tiny? That's 1080x1920.
HOW COME QUOTES ALWAYS GO TO THE BOTTOM OF YOUR POST BUT DRAG&DROP IMAGES ALWAYS GO TO THE CURSOR POSITION!?
Jesus, if you're going to be buggy and shitty at least be consistent. Whenever I do something that auto-inserts text into my posts, I never have any way to figure out where it'll end up.
-
@anotherusername properties... of a file from the internet... in winxp... in 2016...
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGH!
-
@Magus said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
properties... of a file from the internet... in winxp... in 2016...
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGH!Yes, I fired up my XP Mode VM to capture the screenshot because the Windows 7 properties dialog doesn't even show the image's DPI (apparently that's not important to anyone) but does include information that I'd need to redact. But okay, here:
(and yes, it's the actual DPI embedded in the file; I just created a PNG with a DPI of 12345, and the Properties dialog displayed it correctly)
EDIT: apparently Win7 does show the DPI, but only in Explorer, in Details view, if you modify the displayed columns and scroll through the huge list of properties to find and add those columns to the display (they're not shown by default). So there's your Win7 version:
-
@Onyx said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
And now let us all collectively wonder why in the fuck would you need that.
For the same reason people think they need 20+MP cameras?
Going to high on the resolution can actually suck. My Galaxy Note II is more responsive when playing games, because it's 720x1280, compared to my LG G3, with a 1440x2560 display, even though the latter's got a significantly faster CPU and better GPU.
-
@Onyx said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
And now let us all collectively wonder why in the fuck would you need that.
Mobile? That's different
SONY but it's 4K
Discourse now on mobile
There may be some bugs
WORKS AS EXPECTED!
-
This post is deleted!
-
@fbmac Darn you! I'm sorely tempted to instance a Sockbot after you to quote all your posts before you delete them!
-
@Tsaukpaetra I would just create a new user
-
@fbmac said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
I would just create a new user
Ah, but your action patterns would mark you!
Tempted to post in the Evil Ideas thread...
-
@Tsaukpaetra so you would put an AI in your bot?
-
@fbmac said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
so you would put an AI in your bot?
....
Oh, you're not talking about myself.
Well, sure! There are pattern recognition programs, I could just apply them to all the posts of a given user, compare them to the output of another user, and see if that matches well enough to consider them the same!
This could actually end the discussion of all of @blakeyrat's and @boomzilla's alts though, which would expose a mass portion of the active forum, so.... maybe I shouldn't,,,,
-
@Tsaukpaetra said in This thread was not (and still isn't) titled "Through A Mobile CSS, Darkly":
pattern recognition
Wrong sci-fi author ...