It would be naive to think you can run an independent/secure cryptoapp based in the US.
Published source makes it a lot easier to spot problems with the code.
Also, with published source code you can, with the appropriate license, legally recompile it yourself using your own set of tools as a hedge against the publisher's tool-chain or binary-repository being compromised.
Granted, if your tools (anything from the bare metal on up) is compromised or if you are using it to talk with someone else who is using a different binary, all bets are off.
As one who worked at Apple stores for 9yrs 2% of users upgraded ram after purchase.
2% - that you know of. How many upgraded without ever informing Apple (oh please don't tell me Apple "phones home" and gives this "valuable research information" to Apple without informing the users, please don't tell me that).
Every Mac I've ever owned got either more RAM, a bigger drive, or both before I retired it, all without any help from Apple. Some of them even served as Linux or other no-MacOS boxes once Apple stopped allowing any supported version of macOS to run on the old hardware.
Macs are worth 75% retail value after 2 years
Yes, yes, very much yes. I do buy used. Howerver, I won't be buying any of the recent-vintage used Mac notebooks precisely because they aren't user-upgradeable.
The purpose of labs and other homework is to practice. If you cheat, it's a waste of time.
Proving your skills to the instructor needs to be done in a controlled environment. "Controlled" doesn't always mean audited: In a perfect world a student's sense of ethics would be enough self-control that take-home tests or graded projects would be allowed as nobody would collaborate or use others' work beyond the bounds imposed by the instructor.
If ethics is a problem, either do a better job of teaching ethics, make your program and admissions process such that unethical people won't want to apply, or arrange the material so all work that makes a significant contribution to the final grade is audited in a very-hard-to-defeat manner.
I'm looking for 1kg stone bricks that only weight 100 grams.
I assume you mean you are looking for 1kg stone bricks that only weigh 0.98 Newtons.
You need to find a place with approximately 0.1 earth gravity. You might find a shop that sells stone bricks there, they should be able to meet your needs just fine.
If you are looking for stone bricks that "only weigh 100 grams" you won't find them, as grams measure mass, not weight.
I didn't have significant savings until I was way over 13. I don't remember if I could afford a down payment for a house at age 35 but if I could, it would've been a small one.
What are these "Federal Reserve Notes" of which you speak.
My US Dollars are stored in book-entry form at my bank.
They must be worth something because the grocer store gladly accepts a that piece of plastic along with my PIN that instructs my bank to transfer some of those dollars to his bank in exchange for something that I can eat.
It's about time someone came up with an turnkey-solution front-end/back-end version of Firefox and Chrome.
The front end would work on iOS or for that matter any other operating system and the back end - which would do the rendering and provide the any UI elements prohibited by Apple's rules - would work on the "back end." The back end would work on my PC/macOS/Linux machine or more likely a cloud-virtual machine.
You say Apple wouldn't allow this? Oh, but they already do: Every remote-desktop/VNC/etc. tool does exactly this, and of course much more. A skilled person could probably set up a "on login as user FOO, run firefox in a jail/chroot/sandbox environment" on his server and use existing remote-desktop software to do this today. What's missing is the "turnkey" version that's "plug and go" on both the front-end and back-end side of things - something so easy that most users could get it up and running in less than 10 minutes, assuming they had a public-facing back-end machine or a way to tunnel into a behind-the-firewall back-end machine (which probably is NOT the case for 90% of users, but that's not an iOS issue).
It's not always the font - it's frequently the historical baggage that goes with it, as demonstrated by his early examples of typography associated with Nazi Germany.
Sometimes it is the font. "Sharp, pointy" fonts like some of the Nazi-era examples he used may convey sharpness, strong boundaries, or even authority in many readers. A simple font that looks like a child's less-than-perfect crayon manuscript will likely remind people of children and all of the emotions that come with that.
It's not just fonts either. Pictures that remind people of a time and place that the racist wants to glorify can have the same effect. Hitler at the Berlin Olympics, famous Nazi scientists being given world-class awards, etc. do the trick.
Why is a teen committing sextortion less serious than an adult committing sextortion?
It's not: A teen a month shy of his 18th birthday committing sextortion against someone his own age is about the same as if he had waited two months to do the same thing.
However, morally, it is much different than if he did it 5 years earlier in life and somewhat different than if he did it 5 years later in life.
I'll spare you comparing the maturity and presumed legal culpability of 13-year-old vs. an 18-year-old, I assume those are obvious.
As for an almost-18-year-old vs. a 23-year old: Many jurisdictions treat 17-year-olds as adults for serious crimes already. However, there's a medical argument that people's moral judgement doesn't really reach "adult level" until their early-to-mid 20s. It's one reason why until the late 20th century many countries wouldn't let you vote until you were 21 and many still won't let you hold high- or even mid-level public office until you are 21. It's also the reason that if I were hiring someone for a job that required good moral judgement, I would hire the 23 year old over a 17- or 18-year old if everything else were equal and I might even hire the older person if the younger person were only slightly more suited for the job in all other ways.
As for sextortion or for that matter any other serious crime where lack of moral judgment was a major factor in why the person committed the crime, if I were the jury or judge setting punishment and the law didn't prohibit me from considering age or maturity, I would probably give the older defendant a 10-20% stiffer sentence if I could.
This could be a stupid teen sextoring an ex-girlfreind, a stupid 13 year old being childish and posting nudes of his sister, or a real sexual predator using Facebook to exploit preschoolers.
On the "badness scale," that last one is much, much worse than the other two.
These shouldn't be all lumped together just cecause they all involve minors.
Expect non-US victims whose countries allow it to sue these companies and their officers in local courts.
Of course, there won't be any trial and they won't be able to collect any judgements, but the officers may find themselves unable to travel to those countries without risking being hit with a subpoena or possibly worse.
If "successful" in restricting travel, it may deter other US companies from cooperating with the CIA or buying companies that have cooperated with the CIA in the past.
You didn't read part 2: "and the disk management made it very difficult to actually delete data without waiting a week or more." I don't know if any drive- or drive-bus-controller firmware that intentionally protects data from erasure until a certain time period has passed.
Yes, part 1, "If disk access were managed by code that was "lower than the operating system," is trivially true in today's environment where drives have their own firmware and even hosts have the host-half of the drive bus (be it USB, SATA, or what-not) with its own firmware or equivalent, but good luck updating all of that firmware. There is room for host-side non-firmware code that logically lives "beneath" the operating system or, perhaps, "beside" the operating system in a manner similar to a microkernel service, that can provide this function.
I've written a very high level, back-of-a-paper-napkin idea in this journal entry. Scroll down to the part I added today. There are no doubt holes in the proposal as listed, but I hope it gets people thinking about ways to make it harder for malicious software to delete data "on short notice," thereby making ransomware harder to write and easier to intercept before it erases data for good.
If disk access were managed by code that was "lower than the operating system" and the disk management made it very difficult to actually delete data without waiting a week or more, it would make writing ransomware much more difficult. Such code could live in the drive firmware and/or in an isolated/low-surface-attack portion of the kernel or in a microkernel server.
Yes, there would be a cost, in that you couldn't scrub data or recover disk space for re-use at the drop of a hat, but it would be worth it for most people.
Also, such a system could be defeated but the number of ways it can be defeated is small enough to be manageable.
A remote--triggered anti-theft system automatically precludes a complete factory-reset, at least while it is on.
After all, what good would a remote-trigger anti-theft system do if a theif could just "reset" a stolen laptop before selling it?
In a perfect world, enabling anti-theft would "lock out" a factory-reset and disabling the anti-theft would require a key of some sort.
The key here - pun intended - is that the user needs to be able to factory-reset an "unlocked" device and know with confidence - perhaps because a dedicated/single-purpose LED lights up at the end of a successful reset - that the device reset successfully.
My code rately compiles correctly on the first attempt.
Sure, I could carefully inspect it before clicking "build," but it's faster to go through the build-fix-build cycle a few times than to scrutinize it for compile-time errors beforehand.
As for the rest of the test, I would fail too, especially since it is a one-hour timed test.
Now, show me a problem where the obvious/naive solution is something any decent programmer can get right in half a day but finding an ideal- or nearly-ideal solution will take a great programmer a few hours to find, a very good programmer a day to find, a mediocre one 2 days to find, and a lousy one a week to find if he could find it at all, and I will show you a problem that *might* be worth considering if you are trying to "rate" programmers on coding skill.
It would be naive to think you can run an independent/secure cryptoapp based in the US.
Published source makes it a lot easier to spot problems with the code.
Also, with published source code you can, with the appropriate license, legally recompile it yourself using your own set of tools as a hedge against the publisher's tool-chain or binary-repository being compromised.
Granted, if your tools (anything from the bare metal on up) is compromised or if you are using it to talk with someone else who is using a different binary, all bets are off.
for sale.
Authentic series 2013 United States Federal Reserve Note in good condition with serial number. Face value $1.00.
Only $19.95 plus shipping.
As one who worked at Apple stores for 9yrs 2% of users upgraded ram after purchase.
2% - that you know of. How many upgraded without ever informing Apple (oh please don't tell me Apple "phones home" and gives this "valuable research information" to Apple without informing the users, please don't tell me that).
Every Mac I've ever owned got either more RAM, a bigger drive, or both before I retired it, all without any help from Apple. Some of them even served as Linux or other no-MacOS boxes once Apple stopped allowing any supported version of macOS to run on the old hardware.
Macs are worth 75% retail value after 2 years
Yes, yes, very much yes. I do buy used. Howerver, I won't be buying any of the recent-vintage used Mac notebooks precisely because they aren't user-upgradeable.
I typically upgrade the RAM and storage at least once during the life of my computers.
Apple is nice and worth paying for but without a way to upgrade it 2-3 years from now, I'll get a non-Apple notebook the next time I need one.
boolean done = true; ...
while (!done) {
}
In a class of about 450, they were the only ones who made that fatal mistake.
That's no mistake, that's a test of the compiler's optimizer.
Show me someone doing something creative today in code.
Those obfuscated- and underhanded-programmer ng contest entries come to mind.
The purpose of labs and other homework is to practice. If you cheat, it's a waste of time.
Proving your skills to the instructor needs to be done in a controlled environment. "Controlled" doesn't always mean audited: In a perfect world a student's sense of ethics would be enough self-control that take-home tests or graded projects would be allowed as nobody would collaborate or use others' work beyond the bounds imposed by the instructor.
If ethics is a problem, either do a better job of teaching ethics, make your program and admissions process such that unethical people won't want to apply, or arrange the material so all work that makes a significant contribution to the final grade is audited in a very-hard-to-defeat manner.
This may be an apt description once the biological computing gets up to speed.
I'm looking for 1kg stone bricks that only weight 100 grams.
I assume you mean you are looking for 1kg stone bricks that only weigh 0.98 Newtons.
You need to find a place with approximately 0.1 earth gravity. You might find a shop that sells stone bricks there, they should be able to meet your needs just fine.
If you are looking for stone bricks that "only weigh 100 grams" you won't find them, as grams measure mass, not weight.
I didn't have significant savings until I was way over 13. I don't remember if I could afford a down payment for a house at age 35 but if I could, it would've been a small one.
Just what the world fucking needed, more pedopeso currencies.
I for one prefer to use mature currencies.
What are these "Federal Reserve Notes" of which you speak.
My US Dollars are stored in book-entry form at my bank.
They must be worth something because the grocer store gladly accepts a that piece of plastic along with my PIN that instructs my bank to transfer some of those dollars to his bank in exchange for something that I can eat.
No timeout, full stop.
It's about time someone came up with an turnkey-solution front-end/back-end version of Firefox and Chrome.
The front end would work on iOS or for that matter any other operating system and the back end - which would do the rendering and provide the any UI elements prohibited by Apple's rules - would work on the "back end." The back end would work on my PC/macOS/Linux machine or more likely a cloud-virtual machine.
You say Apple wouldn't allow this? Oh, but they already do: Every remote-desktop/VNC/etc. tool does exactly this, and of course much more. A skilled person could probably set up a "on login as user FOO, run firefox in a jail/chroot/sandbox environment" on his server and use existing remote-desktop software to do this today. What's missing is the "turnkey" version that's "plug and go" on both the front-end and back-end side of things - something so easy that most users could get it up and running in less than 10 minutes, assuming they had a public-facing back-end machine or a way to tunnel into a behind-the-firewall back-end machine (which probably is NOT the case for 90% of users, but that's not an iOS issue).
Apple is planning to drop 32-bit apps from the app store.
In post-Soviet Cupertino, platform abandons YOU!
It's not always the font - it's frequently the historical baggage that goes with it, as demonstrated by his early examples of typography associated with Nazi Germany.
Sometimes it is the font. "Sharp, pointy" fonts like some of the Nazi-era examples he used may convey sharpness, strong boundaries, or even authority in many readers. A simple font that looks like a child's less-than-perfect crayon manuscript will likely remind people of children and all of the emotions that come with that.
It's not just fonts either. Pictures that remind people of a time and place that the racist wants to glorify can have the same effect. Hitler at the Berlin Olympics, famous Nazi scientists being given world-class awards, etc. do the trick.
Why is a teen committing sextortion less serious than an adult committing sextortion?
It's not: A teen a month shy of his 18th birthday committing sextortion against someone his own age is about the same as if he had waited two months to do the same thing.
However, morally, it is much different than if he did it 5 years earlier in life and somewhat different than if he did it 5 years later in life.
I'll spare you comparing the maturity and presumed legal culpability of 13-year-old vs. an 18-year-old, I assume those are obvious.
As for an almost-18-year-old vs. a 23-year old: Many jurisdictions treat 17-year-olds as adults for serious crimes already. However, there's a medical argument that people's moral judgement doesn't really reach "adult level" until their early-to-mid 20s. It's one reason why until the late 20th century many countries wouldn't let you vote until you were 21 and many still won't let you hold high- or even mid-level public office until you are 21. It's also the reason that if I were hiring someone for a job that required good moral judgement, I would hire the 23 year old over a 17- or 18-year old if everything else were equal and I might even hire the older person if the younger person were only slightly more suited for the job in all other ways.
As for sextortion or for that matter any other serious crime where lack of moral judgment was a major factor in why the person committed the crime, if I were the jury or judge setting punishment and the law didn't prohibit me from considering age or maturity, I would probably give the older defendant a 10-20% stiffer sentence if I could.
33 of the cases reviewed involved children
This could be a stupid teen sextoring an ex-girlfreind, a stupid 13 year old being childish and posting nudes of his sister, or a real sexual predator using Facebook to exploit preschoolers.
On the "badness scale," that last one is much, much worse than the other two.
These shouldn't be all lumped together just cecause they all involve minors.
Expect non-US victims whose countries allow it to sue these companies and their officers in local courts.
Of course, there won't be any trial and they won't be able to collect any judgements, but the officers may find themselves unable to travel to those countries without risking being hit with a subpoena or possibly worse.
If "successful" in restricting travel, it may deter other US companies from cooperating with the CIA or buying companies that have cooperated with the CIA in the past.
You didn't read part 2: "and the disk management made it very difficult to actually delete data without waiting a week or more." I don't know if any drive- or drive-bus-controller firmware that intentionally protects data from erasure until a certain time period has passed.
Yes, part 1, "If disk access were managed by code that was "lower than the operating system," is trivially true in today's environment where drives have their own firmware and even hosts have the host-half of the drive bus (be it USB, SATA, or what-not) with its own firmware or equivalent, but good luck updating all of that firmware. There is room for host-side non-firmware code that logically lives "beneath" the operating system or, perhaps, "beside" the operating system in a manner similar to a microkernel service, that can provide this function.
I've written a very high level, back-of-a-paper-napkin idea in this journal entry. Scroll down to the part I added today. There are no doubt holes in the proposal as listed, but I hope it gets people thinking about ways to make it harder for malicious software to delete data "on short notice," thereby making ransomware harder to write and easier to intercept before it erases data for good.
If disk access were managed by code that was "lower than the operating system" and the disk management made it very difficult to actually delete data without waiting a week or more, it would make writing ransomware much more difficult. Such code could live in the drive firmware and/or in an isolated/low-surface-attack portion of the kernel or in a microkernel server.
Yes, there would be a cost, in that you couldn't scrub data or recover disk space for re-use at the drop of a hat, but it would be worth it for most people.
Also, such a system could be defeated but the number of ways it can be defeated is small enough to be manageable.
Talking about factory reset is showing your age. These days it is all about continuous update. If the device stops working you buy another one.
"If it breaks, trash it" is for cheap stuff or stuff already at end-of-life, not several-hundred-dollar+ computers with years of useful life in them.
A remote--triggered anti-theft system automatically precludes a complete factory-reset, at least while it is on.
After all, what good would a remote-trigger anti-theft system do if a theif could just "reset" a stolen laptop before selling it?
In a perfect world, enabling anti-theft would "lock out" a factory-reset and disabling the anti-theft would require a key of some sort.
The key here - pun intended - is that the user needs to be able to factory-reset an "unlocked" device and know with confidence - perhaps because a dedicated/single-purpose LED lights up at the end of a successful reset - that the device reset successfully.
Product recall.
My code rately compiles correctly on the first attempt.
Sure, I could carefully inspect it before clicking "build," but it's faster to go through the build-fix-build cycle a few times than to scrutinize it for compile-time errors beforehand.
As for the rest of the test, I would fail too, especially since it is a one-hour timed test.
Now, show me a problem where the obvious/naive solution is something any decent programmer can get right in half a day but finding an ideal- or nearly-ideal solution will take a great programmer a few hours to find, a very good programmer a day to find, a mediocre one 2 days to find, and a lousy one a week to find if he could find it at all, and I will show you a problem that *might* be worth considering if you are trying to "rate" programmers on coding skill.