Having spent time with Muslim friends around Ramadan, I have no doubt that this is due to OVEREATING after sunset and before sunrise. I've seen people pack 3000 calories into 2 meals when they should be getting 1500-2000, especially with the reduced activity levels due to lower energy.
Fasting doesn't give you the ability to break rules of biology.
Ask hospitals in underserved areas. I know of one that had to reject many candidates. American doctors refuse to work in Detroit. They also refuse to work in any specialty where hours are tough.
I am still in academics so I have a question about this. If your company owns this is, what shouldn't they be rewarding you generously for making it? They are making money out of your extra effort/work. I get that employees who want their own ip should have the right but if the company is paying you extra and giving other rewards and removing the headache of managing your own company, is that not good?
shouldn't they be rewarding you generously for making it?
Yes, in theory.
In practice, an employee's power to negotiate wages is limited. At some point, the employee just needs to work to eat/pay rent/etc.
Now, in most areas (of the US), software developers already are paid generously. Even in lower paying secondary markets, software dev are usually paid significantly above local averages.
And, anecdotally, that pay is often for a much "easier" job, where "easier" means less stress and fewer hours than professions that generate similar salaries (engineering, accounting come to mind).
Only if your employment agreement says so. Most people hired as programmers, yes, that's true. People who are hired as other things, and end up automating things, well, that's not so clear.
I didn't think that is true. Have you ever seen legacy code. Some code in Cobol and Fortran still exists and is functional. Redis isn't as old as those ofcourse but everyone who used it will need to change code and docs.
This isn't some isolated word doc that can be fixed with a findall/replaceall command this is backend code connected to many systems.
I am not even a professional developer , I am a researcher/grad student and I have faced such issues with something as new as Tensorflow.
If it is such a big issue, then those who had the problem can fork the repo and change the terminology in their fork. Legacy code that wants to use updated redis won't be affected.
Brown guy in the US here. And Muslim and Pakistani. What kind of racism do you think I face? I felt more discrimination in Pakistan for being short and quiet and not having a deep voice than I ever did in the US for being brown, Muslim and Pakistani.
I have been sent through the express lane many times at airport check-in, I have prayed openly(in a corner) at 2 airports, I have worked with a Christian Republican who dropped me off at a mosque on my request and reminded me of prayer times.
I know this is anecdotal but I firmly believe the issue is pure economics + upgringing. I happen to be a moderately rich Pakistani Muslim from a happy and close-knit family, a white person with less income and/or bad family life will have it much harder in the US than I do and thanks to affarmative action, he will have a much harder time getting into an ivy league school than any member of my family or any rich/happy Black or Hispanic family.
I think that the over clocking cheat is a bit different if they are honest about and say the phone, when overclocked, are actually capable of this. The DSLR image is not possible in any case.
Unless the goal of cheating the benchmark was to target user's who overclock their phones (honestly, who does this?, like %0.0001?), then I would still call it dishonest.
Shouldn't benchmarks reflect what your delivering to consumers?
Honest related question. Do car manufacturers do this with their car's speed tests? I know you can squeeze another 50+ HP out of a VW Golf for example with a chip and a higher octane fuel, but AFAICT the specs you see on their site and at the dealer don't show this extra HP. (I realize VW is a bad example of a company that doesn't cheat their books!).
Agreed. One solution could be restricted access. Government of Maynmar not allowed to access this. Same of Houthi and Yemen or Syrian rebels/Assad etc. Idea 2: it could potentially help hold these government's more accountable if everyone in the world has access to a record and thus proof of what they are doing.
This is the most plausible rationale for doing it with blockchains (see also: many other blockchains)
The whole system appears to rely on a trusted group certifying the [probable] authenticity of an individual's records and Rohingya refugee status, in which case you might as well let them host it on a well-backed up regular database...
It's possible, even easy, to insert fake attestations that biometric B corresponds to identity I. But an append-only log has the advantage over other databases that a simple older-record-wins heuristic is likely to prefer genuine identity records.
A regular database has no way to make it infeasible to insert fake old records. Sure, you can publish checkpoints. But that doesn't work so well when you're up against a government that wants to erase your entire ethnicity.
Isn't the sufficiently determined government with the ability to compromise an organization's computers almost as much of a threat to carry out 51% attacks on its private blockchain as to successfully target distributed copies of database checkpoints?
(In practice, I think the Myanmar government's strategy would simply be to disregard the database rather than to attack it anyway, on the basis the local prejudice against the Rohingya isn't based around their numbers or individual identities but the claim that they are actually Bangladeshi illegal immigrants lying about Myanmar ancestry and land)
Yes, it is a threat. That's why I'm not sure why they're not just using Ethereum. Well, I think I know why -- "let's use Ethereum!" isn't a fundable startup idea. But it's too bad, because I have a feeling Myanmar doesn't have even enough compute power to double-spend a single CryptoKitty.
And yeah, a government would certainly try to ignore facts it didn't like.
The basic result is horribly overfitted, because "account creation minute" and "account creation hour" are two of the parameters. (They split those up because "account creation time" was effectively a unique feature all on its own, and they wanted a 'harder' problem.)
This is basically an exercise in overfitting - they learned to recognize account data using that exact same data, and called it deanonymization. The data fuzzing was a little interesting, but it's still overfitting from top to bottom.
I just read quickly through on my way to work so I did not get to that part.
I was thinking more like using tweet content, language useage(words used, sentence length etc) and ip data into a generative kind of network similar to what is used to fix images with missing content. Then the missing content can be the username and it might be able to at least find very similar users.
