Ich bin ein Fan von Raumfahrtmissionen. Roboter-Raumschiffe sind viel kostengünstiger im Bezug auf ihre wissenschaftliche Leistung als bemannte Missionen.
Not too bad, thanks for trying. I can't parse the 3rd sentence, though.
Dude, read the damn discussion. Yes,/. is broken in a lot of ways, but no, your last two comments simply do not relate to the matter being discussed
Your initial claim was
Now tell me Slashdot Unicode support isn't broken
which is moot since i never said anywhere/.'s unicode support wasn't broken. It simply doesn't exist. Your claim is already invalidated by
you're supposed to know/. is latin1-land
, and then, again, in the damn post you were replying to, i said
[...]even with UTF8 support his message would have looked the same.
which implies that there is no unicode support, because it's fucking subjunctive.
Obviously, you would have seen all this if you actually had read the post and/or discussion you were replying to. Or, you might just be really, really stupid.
I suggest you actually read the post you're replying to, before replying. Better yet, read the entire discussion. Doing so, you may be able to avoid looking like an idiot
Looking at the page source, what i decribed is exactly what you did.
Now, there's the possibility that you're too dumb to remember having set posting style to plain old text, therefore having/. do the breakup and entity encoding for you. If you prefer that, fine. Strikes me as the worse explanation, and still doesn't change the fact that you tried to use UTF8 so you're not at all "not wrong".
And i wouldn't even have bothered replying if it hadn't been for that obnoxious blaming-the-tech
That would only be the problem if he entered valid unicode to begin with. He didn't, so even with UTF8 support his message would have looked the same. Therefore, PEBKAC
Oddly, I am GP.
No idea whether GGP was trolling, i didn't read more than the first line.
GGGP wasn't trolling I believe, but rather trying to be funny (successfully so)
Nordisk Film A/S har till grund för skadeståndsanspråket åberopat följande. NN har uppsåtligen eller av oaktsamhet gjort filmen Beck, Levande begravd tillgänglig för allmänheten och har därigenom gjort intrång i Nordisk Film A/S:s upphovsrätt till filmen. NN är till följd av intrången skyldig att utge dels skälig ersättning dels ersättning för ytterligare skada till följd av intrånget. Skadeståndskravet grundas på den uppladdning som ägde rum den 25 oktober 2010. NN har även laddat upp samma film den 15 maj 2010 men denna uppladdning utgjordes av en avfilmning av biofilmsversionen och var av dålig kvalitet, varför målsäganden valde att beräkna skadeståndet utifrån ett senare tillgängliggörande.
No, this is pure PEBKAC. With your 6-digit uid you're supposed to know/. is latin1-land(*).
You're doing it wrong on multiple levels. starting with a 2-byte UTF8 char (say, 0xc3a4, the UTF8-equivalent of latin1's 'ä') first you break the sequence up into 0xc3 and 0xa4, already removing all meaning, which you then convert into html-entities, apparently TWICE, so what you end up sending to slashdot actually looks like: { where 123 is half of a utf8 char value, on a site expecting latin1. Ehm.
And then you loudly whine about slashdot being broken, when it (correctly) renders your input like you told it to: { I suppose you're one of the people who curse the their TV, as in, the actual device, if nothing good is on air.
And there's even a preview function. Dammit. You are broken.
(*) That's not to imply I'd support that shit. Slashdot should be UTF8 (but your comment would be broken regardless)
You can correct bugs in a robot's operation software, you cannot correct a human.
Yes you can... it's traditionally called "training".
That isn't quite the same as fixing software bugs. After a fix, the bug is gone. After training, it's more likely that the worker won't mess up certain tasks, however, you cannot train away human error.
A human is subject to fatigue and emotions whereas a robot never tires,
Machines don't have wear-and-tear?
The difference here is easily available replacement parts. Bad rotary encoder? Replace it. Bit harder for human parts.
never has a bad day, always operates at peak efficiency.
a tiny, high pressure air nozzle that sweeps across from just below the windscreen.
Wow, are you serious?
This is such a dumb proposal, I don't even know how to point out the flaw. Thinking of a car which is moving through air, the fallacy should be pretty obvious, though.
I can still tell when a CRT is turned on in another room
Oh yeah, dammit this used to drive me nuts when i was younger.. Now I'm pretty close to 30 and... to be honest I haven't been near a CRT in/ages/ so I really can't tell whether I'd still hear it.
Who is porting things to FreeBSD except FreeBSD people?
Who is porting things to Lunix except Lunix people?
Who is porting things to Windows except Windows people?
Still storing personal SSH keys in plain text, by default,...
You mean like every other Unix utility out there?
Oh please. Yes, every other unix does it like that, and Linux, too. However what is stored in plain text is the public key, there isn't anything wrong with that to begin with.
Making it inaccessible by whatever means would defeat its purpose
Slashdot Mirror
Well why would you write comments that disagree anyway?
OAuth2 like would be interdasting.
Would it? Well, OAuth's lead designer politely disagrees
You didn't honestly think /. wouldn't have its share of Microsoft fanboys?
Best Regards, A member of the BSD fanboy fraction.
Ich bin ein Fan von Raumfahrtmissionen. Roboter-Raumschiffe sind viel kostengünstiger im Bezug auf ihre wissenschaftliche Leistung als bemannte Missionen.
Not too bad, thanks for trying. I can't parse the 3rd sentence, though.
blocking.
Yes,
Your initial claim was
Now tell me Slashdot Unicode support isn't broken
which is moot since i never said anywhere /.'s unicode support wasn't broken. It simply doesn't exist. Your claim is already invalidated by
you're supposed to know /. is latin1-land
, and then, again, in the damn post you were replying to, i said
[...]even with UTF8 support his message would have looked the same.
which implies that there is no unicode support, because it's fucking subjunctive.
Obviously, you would have seen all this if you actually had read the post and/or discussion you were replying to.
Or, you might just be really, really stupid.
I suggest you actually read the post you're replying to, before replying. Better yet, read the entire discussion. Doing so, you may be able to avoid looking like an idiot
Eh, I guess it's kind of pointless to try work around not-supported unicode by simply writing a comment in unicode.
Looking at the page source, what i decribed is exactly what you did. /. do the breakup and entity encoding for you.
Now, there's the possibility that you're too dumb to remember having set posting style to plain old text, therefore having
If you prefer that, fine. Strikes me as the worse explanation, and still doesn't change the fact that you tried to use UTF8 so you're not at all "not wrong".
And i wouldn't even have bothered replying if it hadn't been for that obnoxious blaming-the-tech
That would only be the problem if he entered valid unicode to begin with. He didn't, so even with UTF8 support his message would have looked the same. Therefore, PEBKAC
Oddly, I am GP.
No idea whether GGP was trolling, i didn't read more than the first line.
GGGP wasn't trolling I believe, but rather trying to be funny (successfully so)
Nordisk Film A/S har till grund för skadeståndsanspråket åberopat följande. NN har uppsåtligen eller av oaktsamhet gjort filmen Beck, Levande begravd tillgänglig för allmänheten och har därigenom gjort intrång i Nordisk Film A/S:s upphovsrätt till filmen. NN är till följd av intrången skyldig att utge dels skälig ersättning dels ersättning för ytterligare skada till följd av intrånget. Skadeståndskravet grundas på den uppladdning som ägde rum den 25 oktober 2010. NN har även laddat upp samma film den 15 maj 2010 men denna uppladdning utgjordes av en avfilmning av biofilmsversionen och var av dålig kvalitet, varför målsäganden valde att beräkna skadeståndet utifrån ett senare tillgängliggörande.
No, this is pure PEBKAC. With your 6-digit uid you're supposed to know /. is latin1-land(*).
You're doing it wrong on multiple levels.
starting with a 2-byte UTF8 char (say, 0xc3a4, the UTF8-equivalent of latin1's 'ä') first you break the sequence up into 0xc3 and 0xa4, already removing all meaning, which you then convert into html-entities, apparently TWICE, so what you end up sending to slashdot actually looks like: { where 123 is half of a utf8 char value, on a site expecting latin1. Ehm.
And then you loudly whine about slashdot being broken, when it (correctly) renders your input like you told it to: {
I suppose you're one of the people who curse the their TV, as in, the actual device, if nothing good is on air.
And there's even a preview function. Dammit. You are broken.
(*) That's not to imply I'd support that shit. Slashdot should be UTF8 (but your comment would be broken regardless)
to seem clever by explaining how copying isn't theft
Yes you can ... it's traditionally called "training".
That isn't quite the same as fixing software bugs. After a fix, the bug is gone. After training, it's more likely that the worker won't mess up certain tasks, however, you cannot train away human error.
Machines don't have wear-and-tear?
The difference here is easily available replacement parts. Bad rotary encoder? Replace it. Bit harder for human parts.
Ha! You've never worked with automated robots!
Your bots have ``bad days''?
+1 clever
No way, it's also required for google autocomplete. Without that, what the fuck are we supposed to know what to google for?!
a tiny, high pressure air nozzle that sweeps across from just below the windscreen.
Wow, are you serious?
This is such a dumb proposal, I don't even know how to point out the flaw. Thinking of a car which is moving through air, the fallacy should be pretty obvious, though.
I can still tell when a CRT is turned on in another room
Oh yeah, dammit this used to drive me nuts when i was younger.. Now I'm pretty close to 30 and ... to be honest I haven't been near a CRT in /ages/ so I really can't tell whether I'd still hear it.
no dice on my network - it's all shielded cat6
Who is porting things to FreeBSD except FreeBSD people?
Who is porting things to Lunix except Lunix people?
Who is porting things to Windows except Windows people?
Notice a pattern here?
Still storing personal SSH keys in plain text, by default, ...
You mean like every other Unix utility out there?
Oh please. Yes, every other unix does it like that, and Linux, too.
However what is stored in plain text is the public key, there isn't anything wrong with that to begin with.
Making it inaccessible by whatever means would defeat its purpose
...or you go single-user on the file server for just a minute. no big deal, especially when done outside the normal office hours.
You must be new here
You don't know much about English, yet you're using it.
emigrated to
I really don't see the difference.