I'm 23 and I do NOT use my real name as my email address. My netwide handle is "segin", and quite easily (by third graders likely!) resolved to my real name if you're not a total lasy twat.
If I email you from segin@anything.any, and you find that it's not kgill2@someshit.wat to be offensive, dude, seriously, bugger off.
Very few people I know across the age spectrum use their real name for their email account name, the two that do had their account names assigned to them by their ISP fifteen years ago.
What is the problem with rendering HTML? If it is supposed to serve as a functional digital analogue of paper mail, then HTML rendering is a Good Thing. I can bold crap by actually making the lines thicker with my pen. I can underline by drawing an actual underline. I can make the text oblique by writing it slanted. I can do different font sizes by changing the size of the text I write. Images can be included with Scotch tape or glue. Coloring? Use a different color pen (or a different clicker on a multi-color pen.) There's really nothing to be gained by not supporting HTML - I've heard the arguments against, and they don't stand to scrutiny.
Aside from "running JavaScript", there's no real problem there - I've seen all the arguments against, time and time again, since at least 2001. Advertisement? You can avoid that by merely reading the subject line, and examining the sender (both of which are in the headers.) If you receive legitimate email which has subject lines or senders that cannot be distinguished from spam, then consider bitching at your legitimate senders, or replacing them.
At this point, the only real annoyance is Twitter. Whenever the person is on TV, writes an article/book, or a movie about them is aired, I get a nice little run of DMs. Sigh.
You need to follow someone before they can DM you on twitter. Tell another lie.
My address (which you can see unobfuscated right in this comment's metadata!), or most account names, if they have a six-or-more character minimum, is in the form of segin. Except in the case in which I have to create a new account in the same year (due to technical issues with the account, or I botched some WORM metadata, like date-of-birth), then I use _whatever as the prefix.
I could care less if it looks professional or not (or being spied on, if someone spies on my accounts, I feel sorry for them.) The only email address I have that the account name is based on my real name is a mere redirect to my Gmail account.
This alone is an important reason to use your own domain. You can forever be in control of your own email address meaning you can have the address for life or as long as your financial, legal, and/or mental and/or physical health allow.
You can craft your data (it doesn't have to be a font, well, in this specific case it does, but the technique in general doesn't care what format) so that the function loading data will keep loading data past the end of the chunk of memory it allocated for that data. And if you keep on going, you start overwriting other bits of data, such as the address where code execution should resume once the loader function finishes. Now you just replace that address with one pointing to your "data", and make your data actually be code.
Volia, you now have this program running random code you included as part of a "data" file, which can do anything that program can do with it's given credentials. This is a buffer overflow exploit.
Thankfully I live in Canada so this law won't effect all the people I know that rely on wood furnaces for heat and would likely have to invest $10,000+ if they ever had to switch away from wood as a fuel source.
Requirements for new devices do not affect existing installations. Not all of us Americans are so stupid that we can't see you spinningthetruth
Kids naturally start counting at zero. "I have zero breakfast from my parents today, I'll be fed for zero dollars at school." "I'll learn zero about... today..."
Except the crap in the "Promotions" label turns out to be third party crap listservs, wholly unrelated to nor which came from Google, that you signed up for when you ordered that new hard drive from Amazon or put your email address on that paper form when you signed up for your Staples Rewards card. This is random shit you would have appear in your inbox (assuming you aren't using filters) regardless of whom you choose your email provider to be.
Now, if Microsoft called it the "Screwhoo!" campaign, that'd actually have at least a tiny bit of truth to it. I used the Yahoo! Mail app on my Android device to check my Yahoo! Mail inbox for the first time in who-knows-when and there was an actual "sponsored" item at the top of my inbox that wasn't even email, but a direct advertising link! Screenshot.
This generally boils down to games or other consumer-specific software that use undocumented or release-specific functionality or behavior (or third party middleware that does such), or invent their own way of handling certain things prior to such behavior being "standardized" in the OS. Software written before widespread consumer adoption of NT-derived Windows releases that stores configuration data in it's install directory, for example. (While there is file system virtualization for such applications in some recent releases of Windows, it's not foolproof.)
There are always things that an application can do to limit it's ability to run on future operating system releases. Relying on undocumented, poorly documented, or implementation-specific behavior will generally cause your application to require (a) specific OS release(s).
OS updates aren't so much a concern here (assuming that these devices will never be on "untrusted" networks - yes, a stretch), but Android has excellent backwards-compatibility. Applications designed for Android 1.0 will generally run on Android 4.3 without issue, within reason (given there are certain things you can do with an application on any OS that'll hinder backwards-compatibility, such as relying on certain system behaviors.)
Surface 2 release date is set for October 22, not two years, and these don't have to be certified.
Something that can show your flight maps and NOTAMS today will show the same in two years.
From TFA:
Delta plans to test the tablets on its Boeing 757s and 767s, which are flown by the same group of pilots. The airline is hoping for Federal Aviation Administration approval next year to use the tablets throughout a flight, and it hopes to be using the devices on all of its other planes by the end of next year.
If certification is not required, then why are they waiting for FAA approval? Yes, they don't expect it to take two years (more like six to nine months), but regardless, what does the release date on the device matter if you still have to wait for approval? Or is TFA just plain wrong on the whole requiring approval thing?
TFA says they're buying Surface 2 tablets, not Surface Pro 2. Which use ARM processors. Which cannot run malware designed for x86. Which mostly invalidates your argument.
And then compare the amount of architecture or ARM-capable Windows malware with that which only operates on the Intel IA-32 and/or IA-32e architecture(s).
Slashdot Mirror
I'm 23 and I do NOT use my real name as my email address. My netwide handle is "segin", and quite easily (by third graders likely!) resolved to my real name if you're not a total lasy twat.
If I email you from segin@anything.any, and you find that it's not kgill2@someshit.wat to be offensive, dude, seriously, bugger off.
Very few people I know across the age spectrum use their real name for their email account name, the two that do had their account names assigned to them by their ISP fifteen years ago.
So anything not my real name is grossly inappropriate? So, e.g. I should not use segin@somerandomdomain.net?
sudo make me a sandwich
What is the problem with rendering HTML? If it is supposed to serve as a functional digital analogue of paper mail, then HTML rendering is a Good Thing. I can bold crap by actually making the lines thicker with my pen. I can underline by drawing an actual underline. I can make the text oblique by writing it slanted. I can do different font sizes by changing the size of the text I write. Images can be included with Scotch tape or glue. Coloring? Use a different color pen (or a different clicker on a multi-color pen.) There's really nothing to be gained by not supporting HTML - I've heard the arguments against, and they don't stand to scrutiny.
Aside from "running JavaScript", there's no real problem there - I've seen all the arguments against, time and time again, since at least 2001. Advertisement? You can avoid that by merely reading the subject line, and examining the sender (both of which are in the headers.) If you receive legitimate email which has subject lines or senders that cannot be distinguished from spam, then consider bitching at your legitimate senders, or replacing them.
At this point, the only real annoyance is Twitter. Whenever the person is on TV, writes an article/book, or a movie about them is aired, I get a nice little run of DMs. Sigh.
You need to follow someone before they can DM you on twitter. Tell another lie.
Unless you allow them to DM you without having to follow them.
My address (which you can see unobfuscated right in this comment's metadata!), or most account names, if they have a six-or-more character minimum, is in the form of segin. Except in the case in which I have to create a new account in the same year (due to technical issues with the account, or I botched some WORM metadata, like date-of-birth), then I use _whatever as the prefix.
I could care less if it looks professional or not (or being spied on, if someone spies on my accounts, I feel sorry for them.) The only email address I have that the account name is based on my real name is a mere redirect to my Gmail account.
This alone is an important reason to use your own domain. You can forever be in control of your own email address meaning you can have the address for life or as long as your financial, legal, and/or mental and/or physical health allow.
FTFY.
You can craft your data (it doesn't have to be a font, well, in this specific case it does, but the technique in general doesn't care what format) so that the function loading data will keep loading data past the end of the chunk of memory it allocated for that data. And if you keep on going, you start overwriting other bits of data, such as the address where code execution should resume once the loader function finishes. Now you just replace that address with one pointing to your "data", and make your data actually be code.
Volia, you now have this program running random code you included as part of a "data" file, which can do anything that program can do with it's given credentials. This is a buffer overflow exploit.
Considering Microsoft various âoeGet The Factsâ campaigns, more like Scientology mixed with The Nation of Islam
And here I've been hawking RFC 6238 to people as the next best line of defense for end-users all week long.
My bank does not charge overdraft fees for negative balances under $10.
Thankfully I live in Canada so this law won't effect all the people I know that rely on wood furnaces for heat and would likely have to invest $10,000+ if they ever had to switch away from wood as a fuel source.
Requirements for new devices do not affect existing installations. Not all of us Americans are so stupid that we can't see you spinning the truth
So if I smoke a pack a day AND use a wood stove, I'll take twenty years off of my life expectancy?
Sign me up.
Kids naturally start counting at zero. "I have zero breakfast from my parents today, I'll be fed for zero dollars at school." "I'll learn zero about ... today..."
Why does it feel like there's some kind of comment being made here about the National School Lunch Program?
Essentially.
TheRaven64 is not in the sudoers file. This incident will be reported.
Except the crap in the "Promotions" label turns out to be third party crap listservs, wholly unrelated to nor which came from Google, that you signed up for when you ordered that new hard drive from Amazon or put your email address on that paper form when you signed up for your Staples Rewards card. This is random shit you would have appear in your inbox (assuming you aren't using filters) regardless of whom you choose your email provider to be.
Now, if Microsoft called it the "Screwhoo!" campaign, that'd actually have at least a tiny bit of truth to it. I used the Yahoo! Mail app on my Android device to check my Yahoo! Mail inbox for the first time in who-knows-when and there was an actual "sponsored" item at the top of my inbox that wasn't even email, but a direct advertising link! Screenshot.
I wasn't aware that it is possible to write meaningful exploits purely in a .NET language. Even if shellcode is an inline string...
This generally boils down to games or other consumer-specific software that use undocumented or release-specific functionality or behavior (or third party middleware that does such), or invent their own way of handling certain things prior to such behavior being "standardized" in the OS. Software written before widespread consumer adoption of NT-derived Windows releases that stores configuration data in it's install directory, for example. (While there is file system virtualization for such applications in some recent releases of Windows, it's not foolproof.)
There are always things that an application can do to limit it's ability to run on future operating system releases. Relying on undocumented, poorly documented, or implementation-specific behavior will generally cause your application to require (a) specific OS release(s).
OS updates aren't so much a concern here (assuming that these devices will never be on "untrusted" networks - yes, a stretch), but Android has excellent backwards-compatibility. Applications designed for Android 1.0 will generally run on Android 4.3 without issue, within reason (given there are certain things you can do with an application on any OS that'll hinder backwards-compatibility, such as relying on certain system behaviors.)
Delta is a commercial end-user, not a reseller.
Surface 2 release date is set for October 22, not two years, and these don't have to be certified. Something that can show your flight maps and NOTAMS today will show the same in two years.
From TFA:
Delta plans to test the tablets on its Boeing 757s and 767s, which are flown by the same group of pilots. The airline is hoping for Federal Aviation Administration approval next year to use the tablets throughout a flight, and it hopes to be using the devices on all of its other planes by the end of next year.
If certification is not required, then why are they waiting for FAA approval? Yes, they don't expect it to take two years (more like six to nine months), but regardless, what does the release date on the device matter if you still have to wait for approval? Or is TFA just plain wrong on the whole requiring approval thing?
TFA says they're buying Surface 2 tablets, not Surface Pro 2. Which use ARM processors. Which cannot run malware designed for x86. Which mostly invalidates your argument.
And then compare the amount of architecture or ARM-capable Windows malware with that which only operates on the Intel IA-32 and/or IA-32e architecture(s).