Years ago we didn't have a generation trained on smart phones and touch screens. My mom would not have tried it back then. Now, I can see that happening.
It has its uses, especially if you use tools aligned to ITIL. If you try it without the tools, it is a bunch of guidelines and jargon. Not much sense that way.
I was on a team building those tools, so we had to have the courses first, and they didn't stick well. Going through the requirements, they eventually made sense.
Could have been anything. I was thinking in terms of digital video artifacts, and most importantly pointing out how low resolution and analog equipment can make an actual tech demo possible.
The video said he had 32 movies on a card, put it in, and there were 16 videos. I took that to mean a 4*4 grid, even smaller images. So he might have had a lot of leeway with quality.
He might have had success with a limited range of inputs, like news broadcasts with little or no clips to show. Broadcast quality was probably 320*240, or the PAL equivalent, and that can take lots of lossy compression and survive on a CRT. It could look promising but really be near the peak of its ability.
It's not implausible to have something like 2 tone 4*3 blocks, sending a block ID and primary and secondary color, and the decoder assembles the appropriate mosaic. Like pictures made of bunches of other photos, or ASCII art. Good enough to get the message across but little room for improvement.
USB drives should set off monitoring alerts. Plugging in a cell phone to charge, to a USB port, will likely get both devices confiscated. If the employer is following the rules. Portable electronic devices should not be allowed anywhere that has potential connections to secret information. Metal detectors and all.
There should be a review of internet logs, which would have revealed personal email access as described here. Most likely it was overlooked as harmless, or it happened to match a local exception set up as requested.
You people have no idea how this stuff works. It's free on disa.mil and private enterprise can implement most of these security protocols themselves.
It's not 100% foolproof, and its a lot easier to identity a leaker than to stop it. But you need to do a lot of reading before commenting on this stuff.
"After what happened with Snowden, what do you think the odds are that a contractor can both obtain and distribute a NSA document at all without anyone from the NSA noticing ?"
You clearly don't know anything on the subject. Old rules are better enforced, New rules in place, but it is still reliance on humans, and they are imperfect.
Finding the source after a leak is near trivial, which should be a deterrent. But stopping all leaks requires more watchers asking more questions, reviewing more logs, and not making any mistakes.
In hindsight, she exceeded her need to know. Was that detected at the time? Did anyone challenge her? A talented linguist with clean background needs some additional validation for analysis, and someone makes a judgment call not to immediately jump to conclusions, as anyone in signals intelligence would be trained.
Attack with rhetoric if you wish, but your ignorance is on full display.
Stupid? No. But they want to say they took reasonable steps to maintain profitability. No one wants to be named in a lawsuit alleging failure to perform due diligence, and at this point that's the only function of DRM. Not preventing piracy. Lawsuit prevention.
With it cracked, no one can claim it would have prevented piracy, so they can remove it without fearing lawsuits.
Start with the restricted baseline, and remove the stuff meant to prevent this from being useless, like the CRL checks. That's how we fix it. Oh, and document minor deviations that people may want like Defender av updates.
When that fails, patched binaries, signed if needed via Let's Encrypt.
And then we fix by ditching it. Wine or ReactOS or dump it completely.
I won't spend time searching for you, but there are blog posts from softies describing the various attempts over the years to segregate code, and this is the result of that failure.
The evolution of windows from a DOS based illusion to a full client server model on a single computer resulted in a lot of bad decisions. Yes I'm aware of os2 and the parentage of XP via NT, but certain allowances were made so that Windows 98 and ME software would work on XP.
There was no management and grand plan. Reading Charles Petzold and Raymond Chen make that clear. The effort continues. But this is a normal software company trying to ship product, not meet the ivory tower ideal. Hardly a defense, but the info is all out there, mostly documented in this switch to git. Mark Russinovich, SysInternals, Alex Ionescu have the unofficial story, in a sense. How we got here is clear if you know the history.
C# has NGEN, which takes out the JIT compile and makes native code. There's a folder full of these, so it is a space tradeoff. But speed is hardly a problem for C#. And I believe Java can be compiled to native code as well.
If you need performance, it is likely you have a bad algorithm, or are misusing the language, like not using a string builder.
And you can always switch to C/C++ for a true native DLL for anything that needs it.
The stacks are getting faster, if you know how to use them. Not realizing how your ORM translates your request, and making it iterate and transform the results more than once, is a developer problem to be solved by education.
Yes in general the OS gets bloatier, and Windows definitely sucks more. But that's not much impact to custom code. Especially running on a headless server with the bare minimum install.
It's their time, they can spend it however. Personally, I've seen enough struggle with old software on Windows 10 that having drop-in user mode libraries to debug at source level might be useful. Just being able to see the arguments passed in might make the difference in creating a custom solution or just providing a shim to make it work.
Classic Shell is no longer open source, but ReactOS is devoting effort to make explorer work as a drop in replacement. Use it as the shell on vista or server 2003, fix what it doesn't do right, then fix reactos, or Wine, so it behaves. Just that component alone is worth it to me.
Not sure how it works with later versions, but the source is there and available. The recent theming work is almost certainly in Explorer and related components, and likely fixes issues not uniquely within the scope of themes.
You talk with authority about something you never heard of before.. The entire point is that it works and acts like Windows. The UI is not a perfect match, but functionally it is the same. The learning curve is no more than a windows version upgrade.
If the goal is to catch abusers, and that's all they caught, I can maybe make an exception. But I have a hard line stance on law enforcement's boundaries, and that sometimes means that guilty men go free.
Even with an enforced upload ratio, it is not guaranteed that an uploader is an abuser. And this is where your argument turns into "downloading is illegal too so catch them all," which is not what you posted.
If you believe that everyone downloading should be prosecuted regardless, as long as we caught them in the dragnet, because simple posession indicates potential issues, then you cannot defend the feds running the site and distributing content. If its that bad, they shouldn't be doing it, simple. "There's a slight chance this person may abuse a child" is in no way a defense for "FBI continued distribution of illegal content." You have to draw the line on posession, and supporting this the way you just did puts your argument on both sides of that line.
For the record, they should have stopped distribution immediately, but allowed the site to function otherwise. Maybe with a technical difficulties message, allowing uploads to work but not be viewed. Not comfortable with that but defensible.
I have a utility that requests the end of a zip, displays the contents, and lets you select files. The compressed data is downloaded, the central directory rewritten, and you saved bytes.
Tell me how useless it is, but this was 20 years ago and range requests were a thing back then.
Best practice for business continuity is to use a product with a support contract behind it.
Yes it rarely breaks, and local IT usually fixes it via StackExchange or Social.Msdn searches. But when you don't have an answer, you can say your admin is on the phone with support, and it's no longer your job on the line.
I realise that most linux advocates don't experience nor understand this type of Fortune 500 corporate culture, but this is the decision engine for Microsoft's terrible direction in most things. Purchasing Office is a cost with benefits that outweigh the cost of not having it. It's operational overhead, and no one will question the decision.
Ideology, future state, compatibility, and all the rest are simply not a factor.
The decision to make the OS and development tools and Office more appy, and mobile friendly, is largely because business will buy it anyway, and the admins get no say, especially when support ends for the non shite version.
GWbasic, 8086, with all of the esoteric peek and poke nonsense, without a lick of comprehension.
Then Turbo Pascal, then why is Pascal so much faster, then a failed attempt to compile and link GWbasic.
Then C, where you can effectively peek and poke all you want. And K&R finally taught me what I was doing.
Learning the hard way is not efficient, so university will try a different path. I don't trust the results of that path unless they have an origin story that starts with curiosity. Then the language used is irrelevant.
More likely, based on the description, is that the functionality does not exist, so people don't use it. If they needed it, they would ask for it.
Now there is a community of like minded people who don't need this new thing, and they mostly agree, since no one suggested it.
Some new guy comes in and points out that your software is defective or deficient. Even if you didn't write it, you feel protective and defensive. It's mentally easier to write off the suggestion, than consider that people who aren't you might want or need minor tweaks.
It's Wikipedia Syndrome, where minor improvements are seen as unnecessary because they weren't there before and everyone was happy that way. It's basic sociology, really. Digital Sociology needs to be a thing, applying the field to a new era.
Slashdot Mirror
Years ago we didn't have a generation trained on smart phones and touch screens. My mom would not have tried it back then. Now, I can see that happening.
Same reason the quarter pounder is called a Royale with Cheese in France. Start with 2x4 and cook out some fat and water, you're left with a 2* x 4*.
Also, everyone agreed Size A was dumb.
*pre cooked weight.
As long as they let me filter out the clothed scenes, I'm good with it. Bonus points for being gender specific.
It has its uses, especially if you use tools aligned to ITIL. If you try it without the tools, it is a bunch of guidelines and jargon. Not much sense that way.
I was on a team building those tools, so we had to have the courses first, and they didn't stick well. Going through the requirements, they eventually made sense.
Sometimes, pedantry can be good. You really have to have backup. Remember this.
While it makes a point, that comic also presumes a very narrow set of events.
Could have been anything. I was thinking in terms of digital video artifacts, and most importantly pointing out how low resolution and analog equipment can make an actual tech demo possible.
The video said he had 32 movies on a card, put it in, and there were 16 videos. I took that to mean a 4*4 grid, even smaller images. So he might have had a lot of leeway with quality.
I have 15 mod points, but prefer to personally thank you for exposing pretend expert cunts.
Mo3, Tracker, MOD, all similar or synonyms probably.
He might have had success with a limited range of inputs, like news broadcasts with little or no clips to show. Broadcast quality was probably 320*240, or the PAL equivalent, and that can take lots of lossy compression and survive on a CRT. It could look promising but really be near the peak of its ability.
It's not implausible to have something like 2 tone 4*3 blocks, sending a block ID and primary and secondary color, and the decoder assembles the appropriate mosaic. Like pictures made of bunches of other photos, or ASCII art. Good enough to get the message across but little room for improvement.
USB drives should set off monitoring alerts. Plugging in a cell phone to charge, to a USB port, will likely get both devices confiscated. If the employer is following the rules. Portable electronic devices should not be allowed anywhere that has potential connections to secret information. Metal detectors and all.
There should be a review of internet logs, which would have revealed personal email access as described here. Most likely it was overlooked as harmless, or it happened to match a local exception set up as requested.
You people have no idea how this stuff works. It's free on disa.mil and private enterprise can implement most of these security protocols themselves.
It's not 100% foolproof, and its a lot easier to identity a leaker than to stop it. But you need to do a lot of reading before commenting on this stuff.
"After what happened with Snowden, what do you think the odds are that a contractor can both obtain and distribute a NSA document at all without anyone from the NSA noticing ?"
You clearly don't know anything on the subject. Old rules are better enforced, New rules in place, but it is still reliance on humans, and they are imperfect.
Finding the source after a leak is near trivial, which should be a deterrent. But stopping all leaks requires more watchers asking more questions, reviewing more logs, and not making any mistakes.
In hindsight, she exceeded her need to know. Was that detected at the time? Did anyone challenge her? A talented linguist with clean background needs some additional validation for analysis, and someone makes a judgment call not to immediately jump to conclusions, as anyone in signals intelligence would be trained.
Attack with rhetoric if you wish, but your ignorance is on full display.
Stupid? No. But they want to say they took reasonable steps to maintain profitability. No one wants to be named in a lawsuit alleging failure to perform due diligence, and at this point that's the only function of DRM. Not preventing piracy. Lawsuit prevention.
With it cracked, no one can claim it would have prevented piracy, so they can remove it without fearing lawsuits.
How about you first? Are you just being mindlessly pedantic?
Start with the restricted baseline, and remove the stuff meant to prevent this from being useless, like the CRL checks. That's how we fix it. Oh, and document minor deviations that people may want like Defender av updates.
When that fails, patched binaries, signed if needed via Let's Encrypt.
And then we fix by ditching it. Wine or ReactOS or dump it completely.
I won't spend time searching for you, but there are blog posts from softies describing the various attempts over the years to segregate code, and this is the result of that failure.
The evolution of windows from a DOS based illusion to a full client server model on a single computer resulted in a lot of bad decisions. Yes I'm aware of os2 and the parentage of XP via NT, but certain allowances were made so that Windows 98 and ME software would work on XP.
There was no management and grand plan. Reading Charles Petzold and Raymond Chen make that clear. The effort continues. But this is a normal software company trying to ship product, not meet the ivory tower ideal. Hardly a defense, but the info is all out there, mostly documented in this switch to git. Mark Russinovich, SysInternals, Alex Ionescu have the unofficial story, in a sense. How we got here is clear if you know the history.
C# has NGEN, which takes out the JIT compile and makes native code. There's a folder full of these, so it is a space tradeoff. But speed is hardly a problem for C#. And I believe Java can be compiled to native code as well.
If you need performance, it is likely you have a bad algorithm, or are misusing the language, like not using a string builder.
And you can always switch to C/C++ for a true native DLL for anything that needs it.
The stacks are getting faster, if you know how to use them. Not realizing how your ORM translates your request, and making it iterate and transform the results more than once, is a developer problem to be solved by education.
Yes in general the OS gets bloatier, and Windows definitely sucks more. But that's not much impact to custom code. Especially running on a headless server with the bare minimum install.
It's their time, they can spend it however. Personally, I've seen enough struggle with old software on Windows 10 that having drop-in user mode libraries to debug at source level might be useful. Just being able to see the arguments passed in might make the difference in creating a custom solution or just providing a shim to make it work.
Classic Shell is no longer open source, but ReactOS is devoting effort to make explorer work as a drop in replacement. Use it as the shell on vista or server 2003, fix what it doesn't do right, then fix reactos, or Wine, so it behaves. Just that component alone is worth it to me.
Not sure how it works with later versions, but the source is there and available. The recent theming work is almost certainly in Explorer and related components, and likely fixes issues not uniquely within the scope of themes.
But is it web scale?
You talk with authority about something you never heard of before.. The entire point is that it works and acts like Windows. The UI is not a perfect match, but functionally it is the same. The learning curve is no more than a windows version upgrade.
If the goal is to catch abusers, and that's all they caught, I can maybe make an exception. But I have a hard line stance on law enforcement's boundaries, and that sometimes means that guilty men go free.
Even with an enforced upload ratio, it is not guaranteed that an uploader is an abuser. And this is where your argument turns into "downloading is illegal too so catch them all," which is not what you posted.
If you believe that everyone downloading should be prosecuted regardless, as long as we caught them in the dragnet, because simple posession indicates potential issues, then you cannot defend the feds running the site and distributing content. If its that bad, they shouldn't be doing it, simple. "There's a slight chance this person may abuse a child" is in no way a defense for "FBI continued distribution of illegal content." You have to draw the line on posession, and supporting this the way you just did puts your argument on both sides of that line.
For the record, they should have stopped distribution immediately, but allowed the site to function otherwise. Maybe with a technical difficulties message, allowing uploads to work but not be viewed. Not comfortable with that but defensible.
And http has range requests.
I have a utility that requests the end of a zip, displays the contents, and lets you select files. The compressed data is downloaded, the central directory rewritten, and you saved bytes.
Tell me how useless it is, but this was 20 years ago and range requests were a thing back then.
Best practice for business continuity is to use a product with a support contract behind it.
Yes it rarely breaks, and local IT usually fixes it via StackExchange or Social.Msdn searches. But when you don't have an answer, you can say your admin is on the phone with support, and it's no longer your job on the line.
I realise that most linux advocates don't experience nor understand this type of Fortune 500 corporate culture, but this is the decision engine for Microsoft's terrible direction in most things. Purchasing Office is a cost with benefits that outweigh the cost of not having it. It's operational overhead, and no one will question the decision.
Ideology, future state, compatibility, and all the rest are simply not a factor.
The decision to make the OS and development tools and Office more appy, and mobile friendly, is largely because business will buy it anyway, and the admins get no say, especially when support ends for the non shite version.
Business continuity above all else.
GWbasic, 8086, with all of the esoteric peek and poke nonsense, without a lick of comprehension.
Then Turbo Pascal, then why is Pascal so much faster, then a failed attempt to compile and link GWbasic.
Then C, where you can effectively peek and poke all you want. And K&R finally taught me what I was doing.
Learning the hard way is not efficient, so university will try a different path. I don't trust the results of that path unless they have an origin story that starts with curiosity. Then the language used is irrelevant.
More likely, based on the description, is that the functionality does not exist, so people don't use it. If they needed it, they would ask for it.
Now there is a community of like minded people who don't need this new thing, and they mostly agree, since no one suggested it.
Some new guy comes in and points out that your software is defective or deficient. Even if you didn't write it, you feel protective and defensive. It's mentally easier to write off the suggestion, than consider that people who aren't you might want or need minor tweaks.
It's Wikipedia Syndrome, where minor improvements are seen as unnecessary because they weren't there before and everyone was happy that way. It's basic sociology, really. Digital Sociology needs to be a thing, applying the field to a new era.