Switch to sodium-vapor lamp and observatories can filter out the narrow notch of orange-yellow light it produces. Or use smart lamps that permit the scheduling of lowering of the level of street lights.
With highways that are mandatory self-driving you could also eliminate street lights and headlights.
Either you believe in the free market, and housing in the Bay Area is correctly priced based on supply and demand. Or you are a socialist that feels that you are are owed something by society and that you should be able to choose to live anywhere you want even if you cannot afford it.
Make sure the illegal alien is an independent contractor so you don't have liability and don't need to pay for insurance, disability, workmans comp, etc. That's just smart business.
Is to prompt the end-user to choose a name for it. It's your device, I shouldn't have to call it "Google" or "Alexa" or whatever. To truly make a device personal, I should be required to name it.
I take it you don't work in the semiconductor industry. A lot of companies I've worked for use Lattice for prototyping. And some open source fanatics have reverse engineered their iCE FPGA and can generate reasonable bitstreams for several models.The FPGA world is more than just Xilinx and Altera, I would say Lattice is a third major player that has more market share than all the other minor players combined. (roughly 6% vs 5%)
You do realize that you can still have plain text email and include images, don't you? They don't have to be inlined to be useful.
I don't find attachments as useful as information that is well presented in context. Perhaps your verbal skills are above average, or at least better than my own, and you find text to be sufficient for anything you might wish to communicate.
I normally don't reply to AC's claiming to be "APK" but I wouldn't want this much misinformation to go unanswered.
First link is addressed in my statement "The only time people run into issues is when a Microsoft Word document (.doc or.docx) is renamed to.rtf and loaded erroneously."
The second link is an OLE exploit and not supported by the RTF version I linked and referred to by the statement "The Rich Text Format from back in the 20th century..."
Third link is a mispaste and doesn't work.
The fourth link refers to an interesting RCE, but I was not able to dig up the mechanism in the few minutes I spent writing this response. Maybe it's a valid reason not to use RTF, maybe it's just a bug in MS Office and associated DLLs and COM components.
Plain-text is not a panacea either, as we all are well aware of Unicode/UTF-8 bugs in several chat and email programs that allow stack smashing and shellcode. Granted those problems are theoretically easier to fix than an HTML5 email client's bugs.
The main limitation to the sanctions is that it is difficult to wire transfers and international banking. North Korea is basically blacklisted in the majority of banks right now. But once you have a way to put money into another party's account, you can arrange for them to acquire and deliver the goods you wish. There is no naval blockade of North Korea, so importing products amounts to putting it on a ship and sailing it right in.
The sanctions are disruptive to North Korea's trade, but not absolute. And being able to move money around grants them a lot of flexibility.
The opening week determines the excitement that moviegoers have about the film BEFORE they see it. Not what artistic or even entertainment value the film may have after further reflection. The whole thing where the media announces some record sales is carefully controlled PR as well, and really only has a very short term impact on public perception of a film.
That said, reviews by non-professional critics tend to follow immediate trends and it becomes a popularity contest. A lot of people like what other people seem to like, if only briefly. These sorts of reviews are basically garbage and obtaining a high signal-to-noise ratio is a requirement for review aggregation like Rotten Tomatoes to provide any value to visitors. Executed poorly, reviews become a popularity contest equivalent to the worst high school mock election and reveal more information about the reviewers than about the material they review.
Microsoft RTF goes back to 1987. I agree that some open standard would be better, but unfortunately RFC 1896 was not widely adopted. My non-MS environement creates and reads RTF documents and emails just fine. And it was a common format in the NeXTstep/OpenStep days. But seriously, I'm not interested in spending too much time bike-shedding this.
How about if you can't say it without red flashing italic large fonts you just don't bother saying it at all? Simple text conveys a lot of information simply. You don't need a.doc or.pdf to convey one page of text.
I think it is reasonable that I want to underline or highlight parts of log files, or other technical information in order to provide context to the discussion. Tools like email should be expressive enough, rather than limiting everyone to the lowest common denominator.
Short story: if you can encapsulate the content of your image in a "plain-text section", JUST SEND THE PLAIN TEXT. You don't need the image after all, now do you?
Diagrams, drawings and photograph are pretty vital in many day to day communications. Want the gardener to trim back a certain hedge? Take a photo and draw a circle around the offending hedge. You perhaps grossly overestimate the language skills of average people. Perhaps if everyone using email were college educated this wouldn't be a problem, but we might have to go to some extreme like providing free college for a few generations for yours to be a reliable assumption.
advertisers are doing me a favor by sending emails crammed full of tracking images. It is so easy to send these kinds of emails to the junk folder with a simple filter.
If I could filter my physical mail based on the color and texture of the paper I would cut out most of the junk mail. (and maybe toss out some of the semi-junk correspondence from businesses I use, hardly a flaw in this plan)
But really, I don't think it is a valid to argue on what Email was "intended" for when it's changed so much in the four decades. The users ultimately get to determine what Email is really for and how it should be used, and not the long retired designers. Unfortunately "users" includes spammers, who exert more influence on how Email is used than they deserve.
The images for DjVu are typically scanned at 300-1200 DPI. Which is higher than your 8K monitor. So your A4 sheet of paper is probably 50% bigger on your 8K display than it would be in real life, you might want to scale it down a little bit to read it if you are close to your screen. There is enough information that you can scale up the bitmap pretty comfortably as well. Of course on a phone it would be downscale pretty significantly.
The main limitation to a bitmap format or really any typeset format is text reflow. The closest equivalent would be PDF, you usually are stuck with however the author chose to form the PDF file. The font sizes, the layout (1 column? 2 column? landscape?). But we had this limitation for hundreds of years using physical correspondence and it wasn't too big of a deal until recently.
Plain-text is the lowest common denominator and I can see the point of the article. But it's not hard to imagine solutions to the problem that are both relatively simple and more expressive than ASCII/UTF-8. Obviously we should discard any sort of e-mail standard (de factor or official) that is inherently insecure.
Wouldn't I be better off making purchasing decisions in a low-pressure and high-information environment like the Internet? My grocery store does fine without having to have a sales person follow me around and convince me to buy oranges or maple syrup.
Having a sales person does make a business a lot more money, which is why they do it. But as a consumer I need them about as much as I need mosquitoes in the ecosystem. (which is to say, easily replaced and non-vital)
The Rich Text Format from back in the 20th century does not support macros and there are no known exploits for it in the last 18 years. The only time people run into issues is when a Microsoft Word document (.doc or.docx) is renamed to.rtf and loaded erroneously. But with e-mail the MIME types and integrated viewer and editor would avoid that file extension hole. (that same hole would exist for.txt if MS Office were the default program for that extension, mostly that's just Office being terrible)
Theoretically a safe subset of HTML is possible, but nobody wants to maintain some subset parser with no standard. (standard might be as simple as HTML3.2 without JavaScript or IMG tags to external sites). Perhaps W3C or others should create an HTML profile for safe email.
Myself I'd rather have the sender render and encode a highresolution bitmap file which compresses bilevel images very well allowing for high resolution (like DjVu format). And tag the image with a plain-text section for screen readers, search and OCR to deal with. You get perfect typesetting and good illustration for your email, with far less complexity of dealing with HTML or RTF layout, font differences between systems, etc. (again my example sucks because nobody standardized it)
Slashdot Mirror
Switch to sodium-vapor lamp and observatories can filter out the narrow notch of orange-yellow light it produces. Or use smart lamps that permit the scheduling of lowering of the level of street lights.
With highways that are mandatory self-driving you could also eliminate street lights and headlights.
Either you believe in the free market, and housing in the Bay Area is correctly priced based on supply and demand.
Or you are a socialist that feels that you are are owed something by society and that you should be able to choose to live anywhere you want even if you cannot afford it.
Make sure the illegal alien is an independent contractor so you don't have liability and don't need to pay for insurance, disability, workmans comp, etc. That's just smart business.
If the democracy falters you will have neither free speech nor free beer.
Let's apply a 1 cent tax on every text message, and we'll see if that motivates you to get involved in democracy.
You are correct sir. My house is named "computer" and my car is named "hal".
Is to prompt the end-user to choose a name for it. It's your device, I shouldn't have to call it "Google" or "Alexa" or whatever. To truly make a device personal, I should be required to name it.
I take it you don't work in the semiconductor industry. A lot of companies I've worked for use Lattice for prototyping. And some open source fanatics have reverse engineered their iCE FPGA and can generate reasonable bitstreams for several models.The FPGA world is more than just Xilinx and Altera, I would say Lattice is a third major player that has more market share than all the other minor players combined. (roughly 6% vs 5%)
You do realize that you can still have plain text email and include images, don't you? They don't have to be inlined to be useful.
I don't find attachments as useful as information that is well presented in context. Perhaps your verbal skills are above average, or at least better than my own, and you find text to be sufficient for anything you might wish to communicate.
I normally don't reply to AC's claiming to be "APK" but I wouldn't want this much misinformation to go unanswered.
First link is addressed in my statement "The only time people run into issues is when a Microsoft Word document (.doc or .docx) is renamed to .rtf and loaded erroneously."
The second link is an OLE exploit and not supported by the RTF version I linked and referred to by the statement "The Rich Text Format from back in the 20th century ..."
Third link is a mispaste and doesn't work.
The fourth link refers to an interesting RCE, but I was not able to dig up the mechanism in the few minutes I spent writing this response. Maybe it's a valid reason not to use RTF, maybe it's just a bug in MS Office and associated DLLs and COM components.
Plain-text is not a panacea either, as we all are well aware of Unicode/UTF-8 bugs in several chat and email programs that allow stack smashing and shellcode. Granted those problems are theoretically easier to fix than an HTML5 email client's bugs.
The Rich Text Format from back in the 20th century
The version of RTF I linked does not support OLE, so your CVE is not effective. Nice try though.
The main limitation to the sanctions is that it is difficult to wire transfers and international banking. North Korea is basically blacklisted in the majority of banks right now. But once you have a way to put money into another party's account, you can arrange for them to acquire and deliver the goods you wish. There is no naval blockade of North Korea, so importing products amounts to putting it on a ship and sailing it right in.
The sanctions are disruptive to North Korea's trade, but not absolute. And being able to move money around grants them a lot of flexibility.
Make it illegal to starve, and punish anyone who does starve.
Is this a rhetorical device? or are you the tool?
With central banking, there is a moderate amount of transparency and regulation. The same can't be said for crypto-currency.
Indeed, if it is a systematic problem then there is even more reason to take action to correct it.
When you can use $600 of silicon to do the job?
The opening week determines the excitement that moviegoers have about the film BEFORE they see it. Not what artistic or even entertainment value the film may have after further reflection. The whole thing where the media announces some record sales is carefully controlled PR as well, and really only has a very short term impact on public perception of a film.
That said, reviews by non-professional critics tend to follow immediate trends and it becomes a popularity contest. A lot of people like what other people seem to like, if only briefly. These sorts of reviews are basically garbage and obtaining a high signal-to-noise ratio is a requirement for review aggregation like Rotten Tomatoes to provide any value to visitors. Executed poorly, reviews become a popularity contest equivalent to the worst high school mock election and reveal more information about the reviewers than about the material they review.
Microsoft RTF goes back to 1987. I agree that some open standard would be better, but unfortunately RFC 1896 was not widely adopted. My non-MS environement creates and reads RTF documents and emails just fine. And it was a common format in the NeXTstep/OpenStep days. But seriously, I'm not interested in spending too much time bike-shedding this.
How about if you can't say it without red flashing italic large fonts you just don't bother saying it at all? Simple text conveys a lot of information simply. You don't need a .doc or .pdf to convey one page of text.
I think it is reasonable that I want to underline or highlight parts of log files, or other technical information in order to provide context to the discussion. Tools like email should be expressive enough, rather than limiting everyone to the lowest common denominator.
Short story: if you can encapsulate the content of your image in a "plain-text section", JUST SEND THE PLAIN TEXT. You don't need the image after all, now do you?
Diagrams, drawings and photograph are pretty vital in many day to day communications. Want the gardener to trim back a certain hedge? Take a photo and draw a circle around the offending hedge. You perhaps grossly overestimate the language skills of average people. Perhaps if everyone using email were college educated this wouldn't be a problem, but we might have to go to some extreme like providing free college for a few generations for yours to be a reliable assumption.
advertisers are doing me a favor by sending emails crammed full of tracking images. It is so easy to send these kinds of emails to the junk folder with a simple filter.
If I could filter my physical mail based on the color and texture of the paper I would cut out most of the junk mail. (and maybe toss out some of the semi-junk correspondence from businesses I use, hardly a flaw in this plan)
But really, I don't think it is a valid to argue on what Email was "intended" for when it's changed so much in the four decades. The users ultimately get to determine what Email is really for and how it should be used, and not the long retired designers. Unfortunately "users" includes spammers, who exert more influence on how Email is used than they deserve.
The images for DjVu are typically scanned at 300-1200 DPI. Which is higher than your 8K monitor. So your A4 sheet of paper is probably 50% bigger on your 8K display than it would be in real life, you might want to scale it down a little bit to read it if you are close to your screen. There is enough information that you can scale up the bitmap pretty comfortably as well. Of course on a phone it would be downscale pretty significantly.
The main limitation to a bitmap format or really any typeset format is text reflow. The closest equivalent would be PDF, you usually are stuck with however the author chose to form the PDF file. The font sizes, the layout (1 column? 2 column? landscape?). But we had this limitation for hundreds of years using physical correspondence and it wasn't too big of a deal until recently.
Plain-text is the lowest common denominator and I can see the point of the article. But it's not hard to imagine solutions to the problem that are both relatively simple and more expressive than ASCII/UTF-8. Obviously we should discard any sort of e-mail standard (de factor or official) that is inherently insecure.
Wouldn't I be better off making purchasing decisions in a low-pressure and high-information environment like the Internet? My grocery store does fine without having to have a sales person follow me around and convince me to buy oranges or maple syrup.
Having a sales person does make a business a lot more money, which is why they do it. But as a consumer I need them about as much as I need mosquitoes in the ecosystem. (which is to say, easily replaced and non-vital)
The Rich Text Format from back in the 20th century does not support macros and there are no known exploits for it in the last 18 years. The only time people run into issues is when a Microsoft Word document (.doc or .docx) is renamed to .rtf and loaded erroneously. But with e-mail the MIME types and integrated viewer and editor would avoid that file extension hole. (that same hole would exist for .txt if MS Office were the default program for that extension, mostly that's just Office being terrible)
Theoretically a safe subset of HTML is possible, but nobody wants to maintain some subset parser with no standard. (standard might be as simple as HTML3.2 without JavaScript or IMG tags to external sites). Perhaps W3C or others should create an HTML profile for safe email.
Myself I'd rather have the sender render and encode a highresolution bitmap file which compresses bilevel images very well allowing for high resolution (like DjVu format). And tag the image with a plain-text section for screen readers, search and OCR to deal with. You get perfect typesetting and good illustration for your email, with far less complexity of dealing with HTML or RTF layout, font differences between systems, etc. (again my example sucks because nobody standardized it)
Love it! Your kids are going to do OK.