Slashdot Mirror
'Why I Decided To Disable AMP On My Site' (alexkras.com)
Web developer Alex Kras on Monday listed a number of reasons why he dislikes Google's AMP project, and why he pulled support for it on his website. From his post: Back in the day we used to have WAP pages -- specific web pages that were presented only to mobile devices. Opting into AMP, for publishers, is kind of like going back to those days. Instead of using responsive design (making sure that one version of the site works well on all devices) publishers are forced to maintain two versions of each page -- their regular version for larger devices and mobile phones that don't use Google and the AMP version. The benefit of AMP is that it imposes tough restrictions on content, making it load fast. The issue with this approach is that AMP becomes a subset of the original content. For example, user comments are often removed. I also find the way images load in AMP to be buggy. AMP tries to load an image only when it becomes visible to the user, rendering a white square instead of the image. In my experience I've seen it fail fairly regularly, leaving the article with an empty white square instead of the image. [...] It's up to publishers to decide if they want to add AMP support on their site. Users, however, don't have an option to turn AMP off. It would be nice if Google provided a user level setting to turn results rendered as AMP off. Unfortunately, even if they were to add this option, it wouldn't help much when Twitter of Facebook would decide to server AMP. Further reading: Kill Google AMP before it KILLS the web - The Register, The Problem With Google AMP, 2 Billion Pages On Web Now Use Google's AMP, Pages Now Load Twice As Fast. John Gruber on open web: Fuck Facebook.
Now if only every other web developer in the world followed suit, and also abandoned the numerous other methods of forcing browsers into crappy "mobile site" ghettos, instead of designing their pages properly, the world would be a better place.
The vast majority of websites become crippled when I browse their mobile version, and I am talking about those "responsive designs" (which the summary seems to indicate they are the "good option"), not just AMP. Even on my 5" phone - i.e. a prime target for "mobile web" content - I usually have to switch to the regular website to retain functionality that I consider essential (but the designers apparently do not). I don't mind having to pan & zoom a bit when everything I need is right there on the page - the only difference is that I use landscape mode.
And that includes slashdot...
Violence is the last refuge of the incompetent. Polar Scope Align for iOS
No day goes by without someone complaining about AMP. This should tell you all you need to know about this technology.
Don't Most mobile browsers allow this now? I know of a LOT of pages with crappy mobile versions. Youtube being one of them. I just go into my page settings and select "Request Desktop Site" and TADA! All is well...
The problem isn't developing a streamlined mobile version of a website, the problem is not dedicating adequate resources to it to ensure it performs well and still satisfies the customer's needs.
If you're big enough to need an alternate mobile website, you're big enough to hire enough people to make it work correctly.
so what if it doesn't compact to remove 1/2 of the info I want to read. Pinch and zoom bitches ...
by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
No day goes by without someone complaining about seat belts. This should tell you all you need to know about this technology.
Not saying that AMP is a good thing, but just because a vocal group of people complain about something doesn't automatically make it a bad thing.
motherfuckingwebsite.com
And in the same way they block indexing by search engines, Facebook forbids The Internet Archive from saving copies of posts.
That's not bad thing though; nothing of value is lost and the storage space could be used for more valuable stuff.
Ezekiel 23:20
A glorious product that has elevated us to the status of Gods. It puts bacon on my table and nurtures my children. I will not hear a disparaging word said against it! Good day to you Sir!
designing their pages properly
Then what's the "proper" way to accommodate the fat fingers of users of touch screen devices without needing excessive scrolling for users with more precise pointing devices? Adding padding around links improves usability on touch screens but increases the scrolling for mouse or trackpad users. And controlling the padding with a CSS media query breakpoint based on viewport width doesn't help because a touch-operated iPad held in landscape orientation has more pixels than a trackpad-operated netbook.
My biggest gripe with AMP is that it breaks same-page-searching. If you have a specific phrase you're searching for on a very long article, it just doesn't work well because all the search results still seem to be rendered underneath the article, and same-page searching seems to go through each of those first, and sometimes still can't find text after that on the AMP page. When I'm looking something up on mobile, I often just want to find a something quick, not read an entire article.
all yall are too stupid to realize if you stop visiting lame websites, that gets site owners attention more than griping about it in forums 0.0042894761% of all intertubes users read. "but zomg that means i'd actually have to sacrifice to make a statement!!!"
I don't whether AMP is responsible, but I visited a site about a week ago with progressive content and image load as I paged down. This is annoying, but nothing new.
Since I wanted to CTRL-F to search within the page, I spent 5 s manually pressing PG-DOWN to fully load the page.
Imagine my horror when I discovered that most of the top of the page—previously loaded already—had now disappeared from my document, and was doing progressive load on the way back up.
That wasn't just irritating. That was outright /etc/hosts-level hellban territory.
Please, for the love of God, look upon my 16 DIMM slots ye Mighty frugal HTTP server, and load the whole damn document all at once, SVP.
designing their pages properly
Then what's the "proper" way to accommodate the fat fingers of users of touch screen devices without needing excessive scrolling for users with more precise pointing devices? Adding padding around links improves usability on touch screens but increases the scrolling for mouse or trackpad users. And controlling the padding with a CSS media query breakpoint based on viewport width doesn't help because a touch-operated iPad held in landscape orientation has more pixels than a trackpad-operated netbook.
I would be happy if mobile Firefox had an option to force line wrapping. Having to keep scrolling horizontally to finish reading sentences, then scroll back for the next sentence, repeat ad nauseum, well that gets old. On some sites this happens whether it's a "mobile" page or not.
APK Hosts File Engine 9.0++ SR-7 32/64-bit https://www.google.com/search?hl=en&source=hp&biw=&bih=&q=%22APK+Hosts+File+Engine%22+and+%22start64%22&btnG=Google+Search&gbv=1/
Ads/script & malware rob speed/security/privacy
Hosts add speed (via hardcodes/adblocks), security (vs. bad sites/malware/poisoned dns), reliability (vs. dns down), & anonymity (vs. dns requestlogs/trackers).
Less power/cpu/ram + IO use vs. DNS/routers/addons/antivirus + less security bugs/complexity & faster vs. addons/routers/remote dns!
* Via what u NATIVELY have in the IP stack in FASTER kernelmode too!
Avoids DNSChangers in routers/IP settings & dns redirects (99.999% of ISP DNS != patched vs. it) + lightens DNS load & resolves faster from local system RAM!
APK
P.S. - Safe https://www.virustotal.com/en/file/e01211ca36aa02e923f20adee0a3c4f5d5187dc65bdf1c997b3da3c2b0745425/analysis/1433430542/
The point of AMP is to restrict what you can do so that pages load faster. And as a side effect, Google gets to make the rules.
But AMP would never have existed if webmasters were a bit more reasonable. We are talking about sites weighting several megabytes for the equivalent of a single blog post, with scripts creatively breaking browsers. With a 2.3MB / 66 object webpage, the author is definitively guilty of this.
How about, instead of complaining about AMP, take the core of the technology, which is actually quite good, remove the Google bits, and make your site even faster and lighter.
when pinching to zoom on articles with small fonts, the layout completely breaks and even becomes totally uncontrollable. It is so bad for me that I switched my default search engine on my phone to Bing to avoid the craziness of AMP. IOS ad blockers work just fine and when i run into a site like the LA Times or Fortune that block it, i just find the same story at another outlet.
The DEVICE knows if it is using a touchscreen or a mouse. It is therefore up to the device to render properly, and the web designer should simply not get in the way of this. I.e. don't think you can force a particular layout so don't even try.
The answer was in the article. Read it sometime.
And yet that's not what the article is about Troll....
Please, for the love of God, look upon my 16 DIMM slots ye Mighty frugal HTTP server, and load the whole damn document all at once, SVP.
Even a PC with double digit GB of RAM can be connected to a satellite or cellular upstream connection whose ISP charges $5 to $10 per GB. Though a non-AMP page like this still loads fast because it's so simple, I imagine people aren't going to be happy to pay the ISP to load images that won't be viewed.
@media
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
It's unclear to which part of the article you are referring. I searched inside the document "I decided to disable AMP on my site" by Alex Kras for the words "touch" and "finger", and neither word was there. I searched for the word "link", and none of the results mentioned adapting link size based on whether the browser uses touch or mouse. Could you quote a sentence from the relevant portion?
And controlling the padding with a CSS media query breakpoint based on viewport width doesn't help because a touch-operated iPad held in landscape orientation has more pixels than a trackpad-operated netbook.
@media
Could you be more specific as to which CSS media query expression you refer?
Isn't that what the "reader mode" button is for?
You know when a fat guy is in the doctor's office, one hand clutching a philly cheese steak, the other hand holding a half-empty party-size bag of doritos. And, in between swigs of a 2-liter Mt Dew bottle, he asks the Dr if there's a pill to help him lose weight, while his coronary arteries beg for the sweet relief of death.
Yeah, that's AMP. most news and blog websites are painful to use on my 4 ghz desktop and are liable to kill my phone's browser. Publishers, you don't need a pill, you need to put down that cheese steak, turn off the 30 different trackers, analytics, taboolas, etc.
The exception is Medium. If you use Medium, kill yourself.
Copyright (c) 1990 - 2014 Dice. All rights reserved. Use of this comment is subject to certain Terms and Conditions.
Expressions using min-width and max-width specified in pixels are a good starting point, as those are compared to the Viewport size reported by the browser. Where you go from there depends entirely on your design needs
All iPad models present a 1024x768 viewport in landscape mode, regardless of how many actual pixels there are. If your content is so crammed together that you can't tap a link with a fat finger on a 7" screen, you need to work on your design a bit.
The shittiest Chromebook I can find presents a 1280x720 viewport. Despite having physically fewer pixels, it presents a larger horizontal viewport dimension than any model of iPad so, yes, you can use media queries just fine. You just have to understand how they work.
For more information on viewport sizes, see here: http://viewportsizes.com/
And if you really can't make it work, consider also using min-width and max-width expressions based on physical size in addition to pixels, so you're measuring physical and virtual capabilities of the device. Even Windows can work accurately with those now.
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
The 'proper' way is to just serve the desktop web page and NOT make a mobile compatible or 'responsive' reskin of your site.
My smartphone has enough resolution and the ability to pan / scan / zoom over all of your content.
I would ask that you not solely use hover-over elements in your UI, but beyond that don't dumb down your website because that doesn''t help me use it from a mobile device. It just pisses me off.
The DEVICE knows if it is using a touchscreen or a mouse.
What if it is a touchscreen device with mouse support, what then?
My smartphone has enough resolution and the ability to pan / scan / zoom over all of your content.
Then what's the proper way to serve the majority of users, who prefer to view documents that are already at a reasonable zoom level when they first load? Search engines behave similarly: Google is known to penalize documents that aren't already at a reasonable zoom level when they first load.
Device stylus.
e.g. PalmPilot
We worked all this shit out decades ago.
The first bad experience I had with it was when I was loading a page strictly to read the comments. I just have my mobile in desktop mode all the time now.
All iPad models present a 1024x768 viewport in landscape mode
So did my first couple PCs (an Acer TravelMate laptop and a Dell Dimension desktop), which had a 1024x768 pixel display and a mouse. My netbook (a Dell Inspiron mini 1012) also has a 1024-pixel-wide viewport because its display is 1024x600 pixels, but it has a trackpad. A full-size PC is likely to have a 960-pixel-wide viewport and a mouse when the user "snaps" a browser window to half of a 1920x1080 pixel screen.
The shittiest Chromebook I can find presents a 1280x720 viewport.
According to the site you linked, the Nexus 10 tablet in landscape orientation also presents as having a 1280-pixel-wide viewport.
Fine-point styli for touch-operated devices still under warranty, such as the Apple Pencil and Samsung S Pen, aren't widespread among most websites' audiences. And a stylus for capacitive touch screens is nearly as imprecise as the finger it's designed to emulate.
When I browse on my phone, I just zoom in if a link is too hard to tap.
You are also aware of the zoom feature. Not all sites' audiences are as technical as that of Slashdot. In addition, the mobile view of Google Search penalizes sites that initially load with text too small or links too close together.
I hear he's hiding out in Shanghai. Ask the locals xD
Because its not supposed to be up to the page what the size of links are. Its supposed to be up to the browser. That was the original intent of HTML, of the Web itself.
br. Disabling AMP doesnt solve the problem that browsers arent reformatting automatically, nor can a web page developer solve that problem. The browser authors need to step up and stop trying to be the next PDF.
"His name was James Damore."
... Gruber has written specifically about AMP. https://daringfireball.net/lin...
If you are a publisher and your web pages don't load fast, the sane solution is to fix your fucking website so that pages load fast, not to throw your hands up in the air and implement AMP.
He has written more about it in the past -- links are in that piece.
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
And if you really can't make it work, consider also using min-width and max-width expressions based on physical size in addition to pixels, so you're measuring physical and virtual capabilities of the device. Even Windows can work accurately with those now.
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
Hell, you know what?
@media (pointer:coarse)
Enjoy.
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
And if you really can't make it work, consider also using min-width and max-width expressions based on physical size in addition to pixels, so you're measuring physical and virtual capabilities of the device. Even Windows can work accurately with those now.
I'm failing to understand how high DPI implies pointer precision, unless you're recommending targeting specific models of Apple kit. Laptops and Android tablets vary so much in DPI that the high end of tablets, which lack a trackpad, is likely to overlap the low end of laptops, which have a trackpad.
Neither IE nor Firefox supports pointer:coarse.
If your content is so crammed together that you can't tap a link with a fat finger on a 7" screen, you need to work on your design a bit.
Phones will have smaller screens and are dead simple to detect with media queries.
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
What if it is a touchscreen device with mouse support, what then?
It goes based on whether a mouse happens to be connected. This can cause documents using the @media (pointer:coarse) media query to change styles when a mouse is connected or disconnected.
Did you just assume the size of my screen and the size of my pointing device? Stop. All bets are off on both.
Furries make the internet go.
It's ''ad nauseam'', you fucking peasant.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
Did you just assume the size of my screen and the size of my pointing device?
Until web browsers support CSS4 media queries, web browsers have to use CSS3 media queries and assume that any device with a viewport narrower than 26em or so has a touch screen, which is a coarse pointer.
So, if a wireless mouse (or maybe pen?) is connected, but not being used, it'll give the targets too small for a finger?
I had never heard of AMP, but reading the description of what it does makes me wonder how anyone could ever be stupid enough to use it.
I don't think the problem is so much the evil companies constantly trying to force stupid stuff like this onto foolish people, but rather to get people to stop being such fools.
The web (for better or worse) is a lot more than just a text-driven Wikipedia article, which sounds more in line with the original intent.
Comment removed based on user account deletion
Mandatory Javascript (mandatory loaded from google cdn) for a restricted subset of HTML?
W.T.F.
1) Define a Subset of HTML
2) Create a Parser
3) Validate the page. When it's AMP display it with your fast parser, if not open a browser
4) ???
5) PROFIT
Why does it need javascript?! Javascript should be FORBIDDEN on "fast" pages.
Browsers need to help there. Chrome does a very good job. firefox not that good. But the worst are websites, which disable the zoomin on purpose, because they know better what fontsize is good for me.
your browser can let you choose.
Did you know, that firefox allows you to use alternative stylesheets in the "view" menu? when a site provides a stylesheet with rel="alternative", you can choose it there. And old mozilla had button navigation for rel="next", rel="previous" links. Browsers had nice features even before html5 ...
It is actually possible to make AMP your only experience, if indeed you are willing to accept AMP's implementation of all of the relevant features and skip things it doesn't support. This feels like a hard pill to swallow at first, but often stripping away that custom stuff is what makes it faster, and it being faster benefits people who aren't coming from Google Search and those who still use desktop browsers as well.
For those who can't stomach full-site AMP, I suggest instead studying the compromises made by AMP and then applying them selectively to your non-AMP site. We did this at my former employer and ended up with a page that loads just as fast on mobile as the AMP pages do, but with additional features that AMP can't support. Since we used progressive enhancement, we were able to serve very similar pages to both but cut out some trickier stuff in the AMP experience.
Unfortunately since I don't work at that place anymore I cannot ask permission to link to it as an example, and thus I understand that I don't have a lot of credibility here. However, there's some good stuff to learn in the design tradeoffs of AMP and I think they are well worth studying to see which subset can apply to you.
"AMP is for ARTICLES, not SITES."
ARTICLES ARE FOR MAGAZINES, NOT WEB SITES.
But I guess you failed to understand that since you've probably never picked up a piece of dead wood in your life.
Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
Sorry but AMP sucks even for articles.
Or as Gruber said before... you could just "fix your fucking web site".
The only people that AMP benefits, is Google. It's a lock-in tool, plain and simple.
Google values page speed very highly and that value is only increasing. They're pushing AMP landing pages and converting ads to AMP too. As a website owner, when Google gives priority to those that have AMP pages over those that don't, it's pretty hard to choose not to offer AMP. Look at the sites that chose not to become mobile-friendly back in 2014. They saw significant drop in rank and traffic. Most won't throw away that traffic just because they don't like everything about AMP. Claim maintaining AMP pages is maintaining 2 versions if you like but for most it's done automatically. Few will have to manually maintain their responsive site and AMP site. WordPress runs a huge percentage of all websites and offers a WordPress-made plugin to automatically generate AMP pages, along with other plugins offering the same, plus native implementation is on the way in future versions. The author claims comments can't be included on his site in the AMP version. AMP most certainly supports comments. His implementation just doesn't. Additionally, the vast majority of website content doesn't contain comments, so it's not a big issue for most, even if it was true that AMP didn't support it.
Jews believe this about others they call goyim/gentiles: Jews = biggest racists of all (for which they "jew guilt" you for no less! They're hypocrites known as thieves all thru history or were Argentines in the 1940 under Perrone, Spanish inquistion, France (1306), Egypt (despoiled/robbed by jews), Arabs (pre & post 1948), England (1330 Edward longshanks), Romans under titus, Russia pogroms and Germany who got rid of them from their nations nazi german's too? No:
1. Sanhedrin 59a: "Murdering Goyim is like killing a wild animal."
2. Abodah Zara 26b: "Even the best of the Gentiles should be killed."
3. Sanhedrin 59a: "A goy (Gentile) who pries into The Law (Talmud) is guilty of death."
4. Yebhamoth 11b: "Sexual intercourse with a little girl is permitted if she is three years of age."
5. Schabouth Hag. 6d: "Jews may swear falsely by use of subterfuge wording."
6. Hilkkoth Akum X1: "Do not save Goyim in danger of death."
7. Hilkkoth Akum X1: "Show no mercy to the Goyim."
8. Choschen Hamm 388, 15: "If it can be proven that someone has given the money of Israelites to the Goyim, a way must be found after prudent consideration to wipe him off the face of the earth."
9. Choschen Hamm 266,1: "A Jew may keep anything he finds which belongs to the Akum (Gentile). For he who returns lost property (to Gentiles) sins against the Law by increasing the power of the transgressors of the Law. It is praiseworthy, however, to return lost property if it is done to honor the name of God, namely, if by so doing, Christians will praise the Jews and look upon them as honorable people."
10. Szaaloth-Utszabot, The Book of Jore Dia 17: "A Jew should and must make a false oath when the Goyim asks if our books contain anything against them."
11. Baba Necia 114, 6: "The Jews are human beings, but the nations of the world are not human beings but beasts."
12. Simeon Haddarsen, fol. 56-D: "When the Messiah comes every Jew will have 2800 slaves."
13. Nidrasch Talpioth, p. 225-L: "Jehovah created the non-Jew in human form so that the Jew would not have to be served by beasts. The non-Jew is consequently an animal in human form, and condemned to serve the Jew day and night."
14. Aboda Sarah 37a: "A Gentile girl who is three years old can be violated."
15. Gad. Shas. 2:2: "A Jew may violate but not marry a non-Jewish girl."
16. Tosefta. Aboda Zara B, 5: "If a goy kills a goy or a Jew, he is responsible; but if a Jew kills a goy, he is NOT responsible."
17. Schulchan Aruch, Choszen Hamiszpat 388: "It is permitted to kill a Jewish denunciator everywhere. It is permitted to kill him even before he denounces."
18. Schulchan Aruch, Choszen Hamiszpat 348: "All property of other nations belongs to the Jewish nation, which, consequently, is entitled to seize upon it without any scruples."
19. Tosefta, Abda Zara VIII, 5: "How to interpret the word 'robbery.' A goy is forbidden to steal, rob, or take women slaves, etc., from a goy or from a Jew. But a Jew is NOT forbidden to do all this to a goy."
20. Seph. Jp., 92, 1: "God has given the Jews power over the possessions and blood of all nations."
21. Schulchan Aruch, Choszen Hamiszpat 156: "When a Jew has a Gentile in his clutches, another Jew may go to the same Gentile, lend him money and in turn deceive him, so that the Gentile shall be ruined. For the property of a Gentile, according to our law, belongs to no one, and the first Jew that passes has full right to seize it."
22. Schulchan Aruch, Johre Deah, 122: "A Jew is forbidden to drink from a glass of wine which a Gentile has touched, because the touch has made the wine unclean."
23. Nedarim 23b: "He who desires that none of his vows made during the year be valid, let him stand at the beginning of the year and declare, 'Every vow which I may make in the future shall be null'. His vows are then invalid."
Really nice people guess all nations are nazis (egypt "despoiling" robbing it, Romans under titus, russian pogro
Jews believe this about others they call goyim/gentiles: Jews = biggest racists of all (for which they "jew guilt" you for no less! They're hypocrites known as thieves all thru history or were Argentines in the 1940 under Perrone, Spanish inquistion, France (1306), Egypt (despoiled/robbed by jews), Arabs (pre & post 1948), England (1330 Edward longshanks), Romans under titus, Russia pogroms and Germany who got rid of them from their nations nazi german's too? No:
1. Sanhedrin 59a: "Murdering Goyim is like killing a wild animal."
2. Abodah Zara 26b: "Even the best of the Gentiles should be killed."
3. Sanhedrin 59a: "A goy (Gentile) who pries into The Law (Talmud) is guilty of death."
4. Yebhamoth 11b: "Sexual intercourse with a little girl is permitted if she is three years of age."
5. Schabouth Hag. 6d: "Jews may swear falsely by use of subterfuge wording."
6. Hilkkoth Akum X1: "Do not save Goyim in danger of death."
7. Hilkkoth Akum X1: "Show no mercy to the Goyim."
8. Choschen Hamm 388, 15: "If it can be proven that someone has given the money of Israelites to the Goyim, a way must be found after prudent consideration to wipe him off the face of the earth."
9. Choschen Hamm 266,1: "A Jew may keep anything he finds which belongs to the Akum (Gentile). For he who returns lost property (to Gentiles) sins against the Law by increasing the power of the transgressors of the Law. It is praiseworthy, however, to return lost property if it is done to honor the name of God, namely, if by so doing, Christians will praise the Jews and look upon them as honorable people."
10. Szaaloth-Utszabot, The Book of Jore Dia 17: "A Jew should and must make a false oath when the Goyim asks if our books contain anything against them."
11. Baba Necia 114, 6: "The Jews are human beings, but the nations of the world are not human beings but beasts."
12. Simeon Haddarsen, fol. 56-D: "When the Messiah comes every Jew will have 2800 slaves."
13. Nidrasch Talpioth, p. 225-L: "Jehovah created the non-Jew in human form so that the Jew would not have to be served by beasts. The non-Jew is consequently an animal in human form, and condemned to serve the Jew day and night."
14. Aboda Sarah 37a: "A Gentile girl who is three years old can be violated."
15. Gad. Shas. 2:2: "A Jew may violate but not marry a non-Jewish girl."
16. Tosefta. Aboda Zara B, 5: "If a goy kills a goy or a Jew, he is responsible; but if a Jew kills a goy, he is NOT responsible."
17. Schulchan Aruch, Choszen Hamiszpat 388: "It is permitted to kill a Jewish denunciator everywhere. It is permitted to kill him even before he denounces."
18. Schulchan Aruch, Choszen Hamiszpat 348: "All property of other nations belongs to the Jewish nation, which, consequently, is entitled to seize upon it without any scruples."
19. Tosefta, Abda Zara VIII, 5: "How to interpret the word 'robbery.' A goy is forbidden to steal, rob, or take women slaves, etc., from a goy or from a Jew. But a Jew is NOT forbidden to do all this to a goy."
20. Seph. Jp., 92, 1: "God has given the Jews power over the possessions and blood of all nations."
21. Schulchan Aruch, Choszen Hamiszpat 156: "When a Jew has a Gentile in his clutches, another Jew may go to the same Gentile, lend him money and in turn deceive him, so that the Gentile shall be ruined. For the property of a Gentile, according to our law, belongs to no one, and the first Jew that passes has full right to seize it."
22. Schulchan Aruch, Johre Deah, 122: "A Jew is forbidden to drink from a glass of wine which a Gentile has touched, because the touch has made the wine unclean."
23. Nedarim 23b: "He who desires that none of his vows made during the year be valid, let him stand at the beginning of the year and declare, 'Every vow which I may make in the future shall be null'. His vows are then invalid."
Really nice people guess all nations are nazis (egypt "despoiling" robbing it, Romans under titus, russian pogro
if I did have that problem and thought it due to lines being too long, I could just resize the browser window and the text will wrap.
A max-width on the body text column does pretty much the same thing. Putting max-width in the CSS rather than waiting for the user to "resize the browser window" does the right thing by default for the majority of people, who do have this problem.
CSS4 media queries anticipate that multiple pointing devices may be connected at once, which is why it defines a concept of "primary pointer" used to evaluate the pointer media property. If the user wants to use the touch screen, he should tell the browser to treat touch as the primary pointer.
I just wish I knew what "AMP" and "WAP" meant in the context of web development. So many people keep using these obscure three-letter abbreviations (obscure for me, at least, because I'm nerdy in ways besides web development); though I realize that this is news for nerds, so all of you knowing what those things mean is good.
I just wish that once, just once, someone would use the full unabbreviated term so that I could know what the abbreviations mean. I don't trust UrbanDictionary to have the correct definition for this context, and my Google-fu is weak.
</WhinyRant>
In theory, I'm inclined to agree that hosting the ads on the publisher's server is probably the most efficient for network data volume, CPU time, and user privacy. But in practice, a publisher selling ad space directly to advertisers faces a few additional difficulties compared to the more common route of going through a broker, such as an ad network or an ad exchange.
I'm interested to read the solutions that you would apply to these problems if you were running an ad-supported website.