Checking mobile users in web pages, with the largest regex up to date
-
@Bulb said in Checking mobile users in web pages, with the largest regex up to date:
The user agent string should really be redefined to always say just “Open Eyes”¹².
Sounds like some kind of Linux hardware. Are you sure it's safe?
-
@error said in Checking mobile users in web pages, with the largest regex up to date:
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
What I meant was "if what they did on the client with jQuery was being done on the server instead",
What you said was
How much more power would Google servers need if jQuery was running server-side? How much of their power bill are we paying for by having that shit run on our clients?
Which doesn't make any fucking sense (you retard).
Your corrected version still doesn't make sense, because (I'll say it slower) jQuery is a DOM manipulation library. That means its purpose is to interact with a loaded document, and alter it, typically by adding interactivity or animations. What the fuck are you talking about, adding it to the server side?
Postbacks are the future
-
@levicki See but consider this:
I hate that Microsoft runs Windows on our computers just to save processing power on their servers!
-
@anonymous234 said in Checking mobile users in web pages, with the largest regex up to date:
@Mason_Wheeler Responding to that once again: what the RFC says is entirely irrelevant if nobody follows it. It's a non-standard.
And comments inside an address? What were they thinking?!
Yeah, some serious crack in there. But to cover what can occur in the real world it's fine to be able to deal with just those that can be used with SMTP, and those can't have any comments.
-
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
polar bear ejaculate
Actually pretty nasty. Would not recommend.
-
@anonymous234 said in Checking mobile users in web pages, with the largest regex up to date:
@Jaloopa Yeah people block temporary email sites nowadays.
Which is a slap to the face. They know they're being pointlessly annoying to users, and they're doubling down on it.
"but the spammers are using these sites too!"
-
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
you have an IQ of a polar bear ejaculate
When I saw this in QooC, I was hoping I would never find the context. I am now sad.
-
@dcon said in Checking mobile users in web pages, with the largest regex up to date:
@topspin said in Checking mobile users in web pages, with the largest regex up to date:
.+@.+
Easy.
I still remember my
machine!username
address...But who actually cares to support those addresses for real?
For email, checking that there's at least one non-space character on each side of an
@
is probably enough to catch most stupid blunders. Beyond that, you're into the “can I deliver a message that the user can receive?” checks, and any RE that can solve that would scare even a seasoned Perl hacker.
-
@HardwareGeek said in Checking mobile users in web pages, with the largest regex up to date:
I am now sad.
What did you expect from Levicki?
-
This post is deleted!
-
@anonymous234 said in Checking mobile users in web pages, with the largest regex up to date:
@levicki See but consider this:
I hate that Microsoft runs Windows on our computers just to save processing power on their servers!I'd be okay with @error's software using my CPU if they let me download their entire application and run it 100% locally with my data never leaving my local network.
(inb4: no, I'm not okay with Windows 10, and it's actually one of the lesser reasons.)
-
@dkf said in Checking mobile users in web pages, with the largest regex up to date:
@dcon said in Checking mobile users in web pages, with the largest regex up to date:
@topspin said in Checking mobile users in web pages, with the largest regex up to date:
.+@.+
Easy.
I still remember my
machine!username
address...But who actually cares to support those addresses for real?
For email, checking that there's at least one non-space character on each side of an
@
is probably enough to catch most stupid blunders. Beyond that, you're into the “can I deliver a message that the user can receive?” checks, and any RE that can solve that would scare even a seasoned Perl hacker.Maybe if you make said regex into a web service it'd then become web-aware and does exactly that
-
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
@anonymous234 said in Checking mobile users in web pages, with the largest regex up to date:
@levicki See but consider this:
I hate that Microsoft runs Windows on our computers just to save processing power on their servers!I'd be okay with @error's software using my CPU if they let me download their entire application and run it 100% locally with my data never leaving my local network.
(inb4: no, I'm not okay with Windows 10, and it's actually one of the lesser reasons.)
Yes, please download our Community Server support forum and run it locally.
-
@error I admit I missed the fragment about it being a support forum. I imagined some weird LOB content management tool or something.
Now that I go back and read what you use it for, I wonder what kind of retard has ordered you to make that feature. I can only think of one use case for that, and the scumbaggery of using client-side resources for what could be done server side is nothing compared to putting hundred paid ads in every forum thread disguised as ordinary links.
-
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
Now that I go back and read what you use it for, I wonder what kind of retard has ordered you to make that feature. I can only think of one use case for that, and the scumbaggery of using client-side resources for what could be done server side is nothing compared to putting hundred paid ads in every forum thread disguised as ordinary links.
That's not what it does. We have no ads nor advertisers.
-
@error then I have no idea what those links might even be for. Are you emulating a tag cloud in some roundabout way? Linking difficult words to their definitions in glossary? Do the user even see those links or is it just for SEO/internal tooling? Is your support forum even a forum at all or did you build an entire different class of software on top of Community Server?
TBH, my bet is no to all the above.
-
@dkf said in Checking mobile users in web pages, with the largest regex up to date:
you're into the “can I deliver a message that the user can receive?” checks, and any RE that can solve that would scare even a seasoned Perl hacker.
'secially given that the only test of deliverability that you know actually works requires actually sending an email. And i'm pretty sure that RegEx ain't Turing complete.
-
@Vixen said in Checking mobile users in web pages, with the largest regex up to date:
And i'm pretty sure that RegEx ain't Turing complete.
It's like you don't know Perl at all, lady @Vixen!
-
@dkf said in Checking mobile users in web pages, with the largest regex up to date:
@Vixen said in Checking mobile users in web pages, with the largest regex up to date:
And i'm pretty sure that RegEx ain't Turing complete.
It's like you don't know Perl at all, lady @Vixen!
I do not, and it scares me that you are appearing to assert that PERL's regular expression engine allows you to program a regex that is itself Turing complete
-
@Vixen said in Checking mobile users in web pages, with the largest regex up to date:
it scares me
That's the normal and correct response to Perl's “RE” engine, yes.
-
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
TBH, my bet is no to all the above.
I was vague because the specifics of the use-case are very specific to the industry I work in, which doesn't have many companies, and so it would reveal my employer.
-
@error I understand and respect that. Though it still seems to me that the actual business requirement to do what that regex is doing is .
-
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
Though it still seems to me that the actual business requirement to do what that regex is doing is .
True. I only commit major s at work when my boss insists he's really, really sure.
-
@Vixen said in Checking mobile users in web pages, with the largest regex up to date:
@dkf said in Checking mobile users in web pages, with the largest regex up to date:
@Vixen said in Checking mobile users in web pages, with the largest regex up to date:
And i'm pretty sure that RegEx ain't Turing complete.
It's like you don't know Perl at all, lady @Vixen!
I do not, and it scares me that you are appearing to assert that PERL's regular expression engine allows you to program a regex that is itself Turing complete
Turing complete doesn't imply "can send emails".
-
Not purely a mobile JS thing but.....
I'm noticing a trend. more and more sites are using some sort of dynamic JS loading library that assumes all requested scripts will be available and aborts the page load entirely if a requested script is made unavailable for any reason. So if you block ad scripts or tracking scripts or the script server goes offline, or the script fails to match the expected checksum..... or you sensibly decide to brows with JavaScript disabled..... then the sites not only don't work right, they don't work at all.
so you know. Graceful degredation of user experience is clearly no longer on the roadmap for these sites.....
-
@Vixen said in Checking mobile users in web pages, with the largest regex up to date:
Not purely a mobile JS thing but.....
I'm noticing a trend. more and more sites are using some sort of dynamic JS loading library that assumes all requested scripts will be available and aborts the page load entirely if a requested script is made unavailable for any reason. So if you block ad scripts or tracking scripts or the script server goes offline, or the script fails to match the expected checksum..... or you sensibly decide to brows with JavaScript disabled..... then the sites not only don't work right, they don't work at all.
so you know. Graceful degredation of user experience is clearly no longer on the roadmap for these sites.....
So they've devolved from webpack? Does using JS extensively cause disruptions of the temporal loop?
-
@_P_ said in Checking mobile users in web pages, with the largest regex up to date:
@Vixen said in Checking mobile users in web pages, with the largest regex up to date:
Not purely a mobile JS thing but.....
I'm noticing a trend. more and more sites are using some sort of dynamic JS loading library that assumes all requested scripts will be available and aborts the page load entirely if a requested script is made unavailable for any reason. So if you block ad scripts or tracking scripts or the script server goes offline, or the script fails to match the expected checksum..... or you sensibly decide to brows with JavaScript disabled..... then the sites not only don't work right, they don't work at all.
so you know. Graceful degredation of user experience is clearly no longer on the roadmap for these sites.....
So they've devolved from webpack? Does using JS extensively cause disruptions of the temporal loop?
Yes.
The best Explanation I can think of is, since the sites that do this skew heavily towards news, entertainment, and other demographics that rely heavily on advertising they are doing this deliberately to break adblockers in a way that cannot be bypassed without disabling the adblocker entirely.
THE DAY I TURN OF MY ADBLOCKER IS THE DAY I CAN FINALLY TRUST THAT ADS SERVED TO ME WILL NEVER AGAIN BE INFECTED WITH MALWARE!
I don't care about ads that want me to buy shit. I ignore them, I care very much about ads that try to steal my shit. That is why I run adblockers.
-
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
@Vixen said in Checking mobile users in web pages, with the largest regex up to date:
to break adblockers in a way that cannot be bypassed without disabling the adblocker entirely.
That's advertiser's pipe dream, but in reality adblockers can do script injection and sooner or later someone will inject the right (and harmless) bits of code from those blocked scripts to make those pages work again.
if the ad blocker has its hands in the right places yeah. a network level blocker like pi.hole could do that, though keeping it up to date with the defeat attempts of the advertizers would be tricky.
If the blocker can gets its fingers deep enough into the browser to redirect the web requests before they are sent it could do that, that would be more robust, but would still be tricky to implement.
But with browsers wanting to get extensions further from their core, and with these "requirejs" type loaders working deep within JS closures that are impossible to break into without access to the JS engine itself (rather than jsut within the js language)
Yeah, that's actually going to be a fairly effective strategy. It's easy for them to keep ahead of the defeat mechanisms.
besides, when i see one of those sites my reaction is always:
-
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
Honest question, why the above posts were downvoted?
wasn't me.
-
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
Honest question, why the above posts were downvoted?
This boomzilla fellow seems to have it out for you.
-
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
some cross-platform GUI?
if you find one let me know.
-
@AyGeePlus How about AWT, everyone loves it and nobody thinks it's ugly or cumbersome to implement
-
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
Honest question, why the above posts were downvoted?
I just did it because everyone else did.
-
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
Those two do have hands in all the right places
Congratulations, I'm now imagining a ad-blocker circlejerking party.
-
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
Honest question, why the above posts were downvoted?
I'm not sure, but I'd guess it has something to do with you saying manipulating webpages is totally unnecessary.
-
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
Honest question, why the above posts were downvoted?
I'm not sure, but I'd guess it has something to do with you saying manipulating webpages is totally unnecessary.
He just pines for the web of 1995, when men were men and didn't need no steenkin' standards.
-
@hungrier said in Checking mobile users in web pages, with the largest regex up to date:
@AyGeePlus How about AWT, everyone loves it and nobody thinks it's ugly or cumbersome to implement
Does it work on all relevant mobile platforms too? With Windows Phone as good as dead at least Java now is portable, but it still has different UI frameworks on the mobile platforms.
The portability story, when including mobile platforms, is still pretty poor. The options I know of are:
- HTML5+JS, using Electron for desktop and Cordova for mobile. JavaScript, WebAssembly is becoming possible to get performance without building native code for each platform.
- Qt. QML+JS and C++ native code, or pure C++.
When you want only desktop there is a couple more libraries (Gtk, WxWidgets) and when you want only mobile also (Xamarin, ReactNative, Flutter), but neither works reasonably on both desktop and mobile. And if you want a web version too, you need to dabble in HTML5+JS anyway, so why not just use it for everything?
-
@Bulb said in Checking mobile users in web pages, with the largest regex up to date:
@hungrier said in Checking mobile users in web pages, with the largest regex up to date:
@AyGeePlus How about AWT, everyone loves it and nobody thinks it's ugly or cumbersome to implement
Does it work on all relevant mobile platforms too? With Windows Phone as good as dead at least Java now is portable, but it still has different UI frameworks on the mobile platforms.
The portability story, when including mobile platforms, is still pretty poor. The options I know of are:
- HTML5+JS, using Electron for desktop and Cordova for mobile. JavaScript, WebAssembly is becoming possible to get performance without building native code for each platform.
- Qt. QML+JS and C++ native code, or pure C++.
When you want only desktop there is a couple more libraries (Gtk, WxWidgets) and when you want only mobile also (Xamarin, ReactNative, Flutter), but neither works reasonably on both desktop and mobile. And if you want a web version too, you need to dabble in HTML5+JS anyway, so why not just use it for everything?
Because people are too embarrassed to admit that JS+electron is actually the best tool for this job. Just like they're too embarrassed to admit that WSL is the best linux repo at the moment.
-
@Vixen said in Checking mobile users in web pages, with the largest regex up to date:
Not purely a mobile JS thing but.....
I'm noticing a trend. more and more sites are using some sort of dynamic JS loading library that assumes all requested scripts will be available and aborts the page load entirely if a requested script is made unavailable for any reason. So if you block ad scripts or tracking scripts or the script server goes offline, or the script fails to match the expected checksum..... or you sensibly decide to brows with JavaScript disabled..... then the sites not only don't work right, they don't work at all.
so you know. Graceful degredation of user experience is clearly no longer on the roadmap for these sites.....
I find it interesting that some sites actually work better without any Javascript than with partially allowed scripts... At least the article's text then tends to be visible somewhere and there's no banners or "veil" over the article reminding you to log in and hand over your tasty personal details.
-
@error said in Checking mobile users in web pages, with the largest regex up to date:
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
Honest question, why the above posts were downvoted?
This boomzilla fellow seems to have it out for you.
-
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
@Bulb said in Checking mobile users in web pages, with the largest regex up to date:
so why not just use it for everything?
Because Javascript is a terrible language with no type safety, no compile-time error checking, a bunch of undefined behavior, a culture of copy-paste and "I'll just pull in this unchecked 3rd party library for this one function I need" programming, and it runs on an UI thread?
That's what the compilers from various sensible languages to JavaScript, asm.js or the newfangled wasm32 are for.
I do agree that using JS for anything complex is a . Unfortunately most things start small (this will be quick and simple in JS, we don't need to set up a transpiler) and outgrow their design.
-
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
I'm not sure, but I'd guess it has something to do with you saying manipulating webpages is totally unnecessary.
But I didn't say that.
I'm pretty sure you did. Maybe you didn't mean to, but when you say a library for manipulating DOM is unnecessary, when DOM is the only way to manipulate the webpage client-side, that's pretty much the only way to read it.
Besides, you can still manipulate them on the server as well.
It's going to work especially well for mouse-over tooltips.
The whole advantage of Javascript seems to be that a bunch of html pages, some iframes and form POSTs were replaced with a single html page with divs and a bunch of XHR requests.
Also, reacting to user input in advanced ways without even having to round-trip to the server. No matter how fast your website loads, it'll never match the speed of client-side script, especially since the latter doesn't have to reload everything (which, among other things, involves losing scroll position and text inputs - sometimes avoidable, but usually not).
At least 80% of the Javascript on the web could be considered malware nowadays because it is either spamming obnoxious popup or popunder ads, autoplaying videos with sound, stuffing modal overlays in your face hiding the content you want to see, moving the page content by delay-showing stuff at the top, using fingerprinting to track you and monetize your browsing habits, using your CPU to mine BitCoin, trying to scam you into downloading "repair" or "antivirus" products, or outright trying to infect your PC or phone with malware.
Agreed. But the other 20% is what differentiates humans from other primates.
To me, any benefits of Javascript for webdev are heavily outweighted by all of the above.
Let's just say I think that live chats, instant form validation, same-page embedded popups, search suggestions, and everything else that was impossible to do without a general purpose scripting language, is a good deal for making it a tiny bit easier to do what everyone and their dog was doing anyway.
@error said in Checking mobile users in web pages, with the largest regex up to date:
He just pines for the web of 1995, when men were men and didn't need no steenkin' standards.
Funny that you mention 'web" and "standards" in the same sentence.
Are you intentionally making it look like you just woke up from 20 year coma? Times of chasing IE bug-for-bug are long gone, it's now a brave, new, HTML5 world with W3C making sure there's a rich, common foundation on which we can all build advanced websites that work on all browsers.
-
@error said in Checking mobile users in web pages, with the largest regex up to date:
He just pines for the web of 1995, when men were men and didn't need no steenkin' standards.
And yet they had them (I am not saying anything about following). Now we only have some fluid goo.
@levicki said in Checking mobile users in web pages, with the largest regex up to date:
Funny that you mention 'web" and "standards" in the same sentence.
They were such attempts. They were long abandoned as hopeless.
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
Are you intentionally making it look like you just woke up from 20 year coma? Times of chasing IE bug-for-bug are long gone, it's now a brave, new, HTML5 world with W3C making sure there's a rich, common foundation on which we can all build advanced websites that work on all browsers.
-
@_P_ said in Checking mobile users in web pages, with the largest regex up to date:
Because people are too embarrassed to admit that JS+electron is actually the best tool for this job.
Whatever it is you're taking, you need either more or less of it.
-
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
Are you intentionally making it look like you just woke up from 20 year coma?
Wait, you mean that wasn't true?
-
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
Are you intentionally making it look like you just woke up from 20 year coma? Times of chasing IE bug-for-bug are long gone, it's now a brave, new, HTML5 world with W3C making sure there's a rich, common foundation on which we can all build advanced websites that work on all browsers.
Are you sure about that? It seems to be rather that "whatever IE does" was replaced with "whatever Chromes does", and W3C ratifying that post-hoc.
-
@topspin said in Checking mobile users in web pages, with the largest regex up to date:
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
Are you intentionally making it look like you just woke up from 20 year coma? Times of chasing IE bug-for-bug are long gone, it's now a brave, new, HTML5 world with W3C making sure there's a rich, common foundation on which we can all build advanced websites that work on all browsers.
Are you sure about that? It seems to be rather that "whatever IE does" was replaced with "whatever Chromes does", and W3C ratifying that post-hoc.
At least it's better than "whatever Safari does", because that'd be even worse.
-
@topspin said in Checking mobile users in web pages, with the largest regex up to date:
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
Are you intentionally making it look like you just woke up from 20 year coma? Times of chasing IE bug-for-bug are long gone, it's now a brave, new, HTML5 world with W3C making sure there's a rich, common foundation on which we can all build advanced websites that work on all browsers.
Are you sure about that? It seems to be rather that "whatever IE does" was replaced with "whatever Chromes does", and W3C ratifying that post-hoc.
The big difference is:
- The "whatever Chome does" is much more than IE ever allowed for, so much that at this point, it's possible to do everything you'd ever want and have it all portable across all browsers and have it work nearly identically everywhere.
- At least there's any standardization at all. You don't have to reverse engineer IE anymore, you can just read the standard - and that's a yuuuuuge plus.
-
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
much more than IE ever allowed for
I mean officially.
-
@Gąska said in Checking mobile users in web pages, with the largest regex up to date:
much more than IE ever allowed for,
IE had a feature Chrome never had: XSS vulnerabilities in your CSS!