_deathcollege
@_deathcollege
https://ibb.co/v1q1mcj this entire site is a honeypot with no actual admin contact. have a nice day.
Best posts made by _deathcollege
-
RE: Advanced Trolly Logic
@boomzilla said in Advanced Trolly Logic:
Solution?
i'd like to see the sub/superset comparison of infinities to best decipher this, please.
-
RE: WTF Bites
We don't sell your data … but if someone can send a selfie with their cop's badge they can have your data for free!
"will no longer" ahahahahaha /me slaps knee
-
RE: WTF Bites
Reddit mobile has been back to terrible-but-technically-usable (from several iterations of literally unusable), so I’ve been reading it on the phone again.
I have noticed many times now, almost but not quite enough to be reproducible, that just zooming in (two finger pinch) makes the page break and reload. I have to zoom in when, e.g., someone posts a cartoon that I can’t otherwise read in the feed, like the Dilbert post above.
Relevant enough: used to break terribly any time I tried that by pushing side bars all over me, but at least that’s been fixed. Heck, it used to do that by scrolling down in an apparently not 100% perfect vertical move.Why does that happen? I guess they want to react to “swipes”, like showing stupid side bars or scrolling through picture galleries when the post contains more than one image. And then their code handles things so horribly when you pinch for a few seconds that it trips all over itself and triggers a reload.
Conclusions:- they’re too stupid to distinguish between actual, intentional “swipes” and zooming, breaking shit to the point where I’m thinking “could you just fucking not do that already?!”
- besides reddit and , I’ve seen many different places fuck things up on zooming. So it’s widespread enough that web devs are apparently not adult enough to handle this correctly.
- if you can’t handle it, don’t. Having these swipe events visible to JS was a mistake to begin with. It breaks basic page navigation. (Also the pages where zooming isn’t possible at all, probably intentionally, are broken by design. But I’m not sure if that’s the same mechanism.) I’d love an option to just completely kill JS access to this.
something something viewport-size="1.0",window-size="mobile","zoom-size="100",viewport-scale="1.0" for pre-head markup indication
#edit number 80 i have never felt more dyslexic in my life than i did in this post
-
RE: WTF Bites
@Bulb the only thing i had even seen which could have explained this was a table error where the data feedback from an output request that doubled the request and cancelled it out. however, this was for a data list/database of names, idk if this would have like, been applicable to, say, a dns query or dns route throughput
if there was like, an ansible or dns table involved, maybe that did it?
-
RE: Can I borrow an apology?
@homoBalkanus i see your cobol and raise you its strong-type listing & calculations twin, virtual basic
-
RE: WTF Bites
@_deathcollege stuff like the rest api is like the equivalent of what smalltalk did for golang or even ajax, with respect to its front end/dev flexibility, but if you're already self-signing the certificates, you may as well go full steam and plug it into something that's actually encrypted properly with ssl
-
RE: WTF Bites
@gleemonk this is like the one time i accidentally uncovered a hidden storage for reportable content in a search engine by typing in %%[IMG="xyzlinkgoeshere"] into a search engine due to the surfaced meta content surfacing from the source archive; much like the spanish inquisition, no one expects to have to report their funny html hack's src feedback to the fbi
-
RE: WTF Bites
@kazitor what, uhhh; :} what language is this? it's like ajax and python are awkwardly chatting at the cafe.
"w".
Latest posts made by _deathcollege
-
RE: The Official Funny Stuff Thread™
you take care, some of us are here to make friends & don't mind hurting you to do it. :) see you
-
RE: The Official Funny Stuff Thread™
@HardwareGeek and you are? i knew i blocked you for a reason before you could even talk to me.
-
RE: The Official Funny Stuff Thread™
@Arantor bitching?
oh, you're english, i guess, or from 4chan or some shit. i don't bitch. i seldom have to say a thing. most of you, though, just go to a shrine of someone else's work after literally not having learned the lesson from your last interactions with them to soothe your sore asses, so, --
not my electric chair, not my problem.
-
RE: The Official Funny Stuff Thread™
@Arantor was that supposed to be a response to what i said? i'd have preferred if it were read. lol.
-
RE: The Official Funny Stuff Thread™
no takers? awe. every website is the same.
-
RE: The Official Funny Stuff Thread™
@Mason_Wheeler said in The Official Funny Stuff Thread™:
where's the so-hungry-i-could-eat-a-crucifixion option?
-
RE: The Official Funny Stuff Thread™
https://youtube.com/watch?v=IV3j0PcS50c&pp=QAFIAQ%3D%3D divine feminine, who is this man who will not get off your wig? zebra cakes are significant, somebody loves zebra cakes. yes; me. get off my wig.
-
RE: WTF Bites
Reddit mobile has been back to terrible-but-technically-usable (from several iterations of literally unusable), so I’ve been reading it on the phone again.
I have noticed many times now, almost but not quite enough to be reproducible, that just zooming in (two finger pinch) makes the page break and reload. I have to zoom in when, e.g., someone posts a cartoon that I can’t otherwise read in the feed, like the Dilbert post above.
Relevant enough: used to break terribly any time I tried that by pushing side bars all over me, but at least that’s been fixed. Heck, it used to do that by scrolling down in an apparently not 100% perfect vertical move.Why does that happen? I guess they want to react to “swipes”, like showing stupid side bars or scrolling through picture galleries when the post contains more than one image. And then their code handles things so horribly when you pinch for a few seconds that it trips all over itself and triggers a reload.
Conclusions:- they’re too stupid to distinguish between actual, intentional “swipes” and zooming, breaking shit to the point where I’m thinking “could you just fucking not do that already?!”
- besides reddit and , I’ve seen many different places fuck things up on zooming. So it’s widespread enough that web devs are apparently not adult enough to handle this correctly.
- if you can’t handle it, don’t. Having these swipe events visible to JS was a mistake to begin with. It breaks basic page navigation. (Also the pages where zooming isn’t possible at all, probably intentionally, are broken by design. But I’m not sure if that’s the same mechanism.) I’d love an option to just completely kill JS access to this.
something something viewport-size="1.0",window-size="mobile","zoom-size="100",viewport-scale="1.0" for pre-head markup indication
#edit number 80 i have never felt more dyslexic in my life than i did in this post