HN user
Does that last bit about "any civil money penalty" mean you can pay your fines with your own meme coin at face value, without having to sell them and thereby tank the value?
Note that she left the Left Party in 1992, and instead joined the Social Democrats. So she's been a member of the national parliament as a representative of the Social Democrats.
This is relevant as the Social Democrats are pro chat control, while the Left Party is against chat control.
Note that in 2013 there weren't many streaming services available in the polled countries. Netflix first appeared in UK and Sweden by 2012, and was probably not available at all in the other polled countries. So it's more likely that TV show prices refer to cable TV, not streaming.
Improved privacy without bad UX is super simple: Have privacy by default, and don't use personal information for things which the user hasn't asked for.
But the metrics/tracking crowd - especially the ad vendors - hate that, and they are more important to most companies/websites than the users.
(It also limits what methods you can use for site improvement, so it's a bit inconvenient for you too.)
Yes and no. The main aspect is that ethereum mining is much bigger than all alternative GPU-mineable coins. When I checked it using whattomine back in January, ethereum mining was roughly 16 times bigger than all others combined.
Since the number of coins mined is fixed regardless of the effort expended, the revenue per card would tank if every ethereum miner switched to other coins.
In their home market in Sweden, they are one of the largest providers of checkout services for e-commerce.
It's pretty much a Stripe competitor, plus BNPL.
The relevant part is this "LAS gäller för alla arbetstagare med undantag för de i företagsledande ställning. Lagen är tvingande, men kan inskränkas genom kollektivavtalsskrivelser."
The law covers all employers and employees regardless of union membership, but agreements between unions and employer organizations can limit the scope.
As you say, in practice companies will often sweeten the deal with a big severance package if they want to make changes which the law doesn't allow. I.e. get the right people to voluntarily resign instead of having the wrong people being laid off.
Turris Omnia ( https://www.turris.com/en/omnia/overview/ ) kind of fits your bill, but it's more 2020 than 2022. The main downside is that it doesn't support WiFi6, so you're stuck with 3x3 MIMO 802.11ac.
It runs a modified OpenWrt, TurrisOS, which is open source.
They're a bit on the pricey side, so "worth buying" from that perspective will be up to you.
Edit: Turns out there might be a 2022 version which would fit your bill (except the time tested part), but it's not launched yet. https://forum.turris.cz/t/turris-omnia-2022/15995/144 https://twitter.com/turris_cz/status/1448535213626200066
As others have said, those other coins will get increased competition splitting the mining returns. Unfortunately (for the miners), Ethereum is vastly bigger than all the other coins.
I checked whattomine a few days ago and compared the hash rates of each coin. To make it simpler to compare, I converted it into RTX3080 equivalents. With this measure the hash rate for Ethereum was equivalent to mining with a bit shy of 10 million RTX3080s.
Ethereum Classic, which is the second biggest coin listed on whattomine, had a hash rate equivalent to about 263000 RTX3080s. I.e. Ethereum has 37 times more miners than Classic, and if they all moved to Classic the revenue would be slashed to 1/38 of what it is now while everybody would incur the same costs as now.
Ravencoin is the second biggest mineable coin (Monero isn't profitable to mine even now, so it does not matter) and Ethereum is 83 times bigger than Ravencoin.
It turns out Ethereum is more than 16 times bigger than every other coin listed on whattomine combined.
In everything except the most exceptional circumstances knowing what to build will be a blend of written requirements and shared knowledge within the team. You can advocate for comprehensive requirements which pushes the effort towards the written spec side, or you can advocate for "working software over comprehensive documentation" which pushes the effort towards using more shared knowledge. Depending on the nature of your project, one or the other might be preferable.
For most projects, both "knowing what to build" and "working software" will never be 100% clear.
My POV from Sweden, where the adoption rate is roughly the same.
From the merchant's perspective:
- There is a law regarding cash registries, to prevent tax evasion by cash accepting businesses. The cost for getting a compliant cash register is probably at least as high as getting an online payment solution set up.
- Not handling cash decreases the risk of robbery.
- Adoption rate is high enough that not accepting cash payments won't lose you many sales, as long as you accept both card and app payments.
- Adoption rate is so high that only accepting cash payments will lose you a lot of sales. I.e. you need to get that online payment solution set up anyway.
- There are several online payment providers (for instance Klarna) which accept app payments.
From the customer's perspective:
- There's an authentication solution (BankID) which is almost used by everyone. You can use it to sign online payments, do your tax returns, and sign the payment app transactions. On your smartphone, this can be done with the fingerprint scanner. I.e. signing a payment isn't harder than unlocking your phone.
- The payment app (Swish) is supported by most Swedish banks and account transfers are instant and free. If I have your cell phone number, I can send you money instantly. This drove adoption amoung young people who already were attached to their phone 24/7.
- Contactless card payments in stores now have a reasonably high limit (400 SEK ~= $45-50), which makes it at least as fast as presenting cash and accepting change.
For me this is at a point where I can't even remember when I last payed with cash, and cash in my wallet is "gone" in the same way that those £25 in small change sitting in a drawer after the trip to the UK are.
They only mention the problem with banks not wanting to handle cash any more, which leaves people who still depend on cash with few options.
Some issues not listed i the article, but which I have noticed here in Sweden:
- Many shops are no longer accepting cash payments, which leaves you unable to transact if you don't have either a payment card (Visa/MC mostly) or the local payment app (Swish).
- Your banks systems doesn't have 100% uptime, and when their systems are being serviced you can't transact.
- Your cellphone carrier doesn't have 100% area coverage, which also makes you unable to transact. If you're a city dweller you probably won't find out until it's too late, and you might have to travel miles to get enough reception to transact.
It seems people reuse the API which is used by the app. An example: https://www.npmjs.com/package/flick-electric-api
So it provides pricing info, not any home automation.
Klarna Inc. is a subsidiary. The parent company is headquartered in Stockholm, Sweden.
There are limitations, namely:
"There must not be a conflict of interest between the duties of the individual as a DPO and her other duties, if any."
Specifically they recommend against also being the data controller. I.e. you shouldn't be responsible both for handling personal data and verifying compliance of said handling.
Somebody could do the TDD movement a great big favour and write a TDD instruction for people who actually already know how to write tests.
There probably are good resources about this somewhere, but compared to the impression of "TDD promotes oceans of tiny, low-value tests" they lack visibility.
UBI will work even in an environment where many people have no marketable skills, while negative income tax would just be the state sponsoring activities with no real value.
We're not there yet, but the odds of ending up there sooner or later is very high.
(Negative income tax could still be good if the activities themselves have a positive social value.)
There were courses using haskell before monads were the smash hit they are now. In particular haskell didn't have monadic IO then. On the other hand, variants such as gofer were pretty simple.
If you don't include the cost of mining hardware, you're probably not making a fair comparison.
(Then you have the philosophical question about what is a reasonable comparison target.)
As most people aren't unique snowflakes when it comes to mate preferences, the likelihood of being the only woman fancying a certain man is low. With Tinder women trade the obnoxious problem of heaps of unwanted attention for the less glaring but quite insidious problem of letting the eligible bachelors know exactly how well off they are. With OkCupid, these men play the same game as everybody else, just with more success. At Tinder they have an exact count of how in demand they are, giving less incentive to commit.
I tend to agree with Tom DeMarco on this issue: "This leads us to the odd conclusion that strict control is something that matters a lot on relatively useless projects and much less on useful projects. It suggests that the more you focus on control, the more likely you’re working on a project that’s striving to deliver something of relatively minor value."
(From http://www.computer.org/cms/Computer.org/ComputingNow/homepa... )
What's up with Bulgaria vs Romania? One's at the top and the other at the bottom.
One case of unexpected behavior which is best described in comments is when the simple and obvious solution to the problem is wrong, and has already been discarded.
(Preferably the reasons for discarding the simple solution should be provided as well, as circumstances may change.)
Maybe not the cheapest solution, but robotic lawn mowers are popular where I live.
My wife asking, “Hey, when you have a minute could you do X?”
This line got me thinking it would be cool with an app where you can ask this kind of things, and the message will only be announced when the user is unlikely to be busy. (Triggered by events such as the phone going from stationary to being moved.) Anybody knows if such an app exists?
It's easy to reply to this phrasing with a canned answer and very little though. "Experience, skill, and a positive attitude." If someone gave this answer to you and you're the candidate asking the question it is basically 0 information.
Although it doesn't say much about the team, I'd say it provides some information on management and the level of transparency vs image management you can expect on the job.
Actually, for a videogame community, the MWO community is pretty mature and helpful. But if people spend $100+ on a promise of a game concept and no progress towards that happens in a couple of years, they will get grumpy even if mild tempered.
I think PGI could have saved themselves a lot of grief by:
- Getting private matchmaking out much earlier than May this year. It's been requested since day one, and would have kept the hardcore folks busy until community warfare.
- Learn the art of tweaking game balance. They drop patches every two weeks. Instead of making huge, sometimes game wrecking, balance changes every three months they could have nudged the balance slightly each patch. "Missiles seem slightly too easy to avoid - making them 3% faster" doesn't make anyone blow a gasket. "Bumping missile speed 75%" will.
Given that it's been a mystery which patents Android might be infringing, what is the likelihood that those patents fill their original purpose of promoting progress? (Beyond the effects obtained by simply implementing them and selling the product.)
Considering Stalin's swift elimination of all his political rivals, it's reasonable to assume not everybody shared his political vision.
It turned out agile processes contained a bunch of important but unpleasant aspects - business people needed to be much more present in daily development, while developers needed to meet with business people much more frequently (often at specific times when said business people were available) and keep lots of non-development action points in mind (as the team now had collective ownership of those action points).
So, in a stroke of mutual back slapping, everybody embraced the less objectionable features of agile methods - daily meetings, short iterations, reduce documentation and focus on shippable code - thus feeling really good about themselves. This caused ample moral licensing, letting most development team members and business people cut down on the unpleasant aspects.
This collective ball dropping was fortunately mitigated by a surplus of employees happy to pick up this poor, unloved ball. Being orderly people they would suggest improvements to the process to prevent further ball dropping, carving out a place and title for themselves while they were at it.