A few days ago I found out that the jetbrains toolbox doesn't actually log you out when you're logging out - they just seemingly stop renewing your token
I found out about it because switching accounts isn't possible, you get logged into your old account unless some time has elapses.
Not a big security issue though, I mean after a day or so it it's actually logged out, just not within the same hour (no idea how long it actually takes - just know it's not within an hour)
Right, under that argument it's their content, their rules then - making this situation even more of a non issue because they're adding this feature themselves.
As a German myself, that list is surprising. The only one I could imagine is 4., because the bins generally aren't watertight, so you're essentially spilling water on the floor which will make a mess for everyone.
And there are always places to pour the water it's just usually at the entrance of the terminal
... Which is obviously dumb, cuz nobody is going to go back to them after they've already queued to get in.
But 1-3? You must've really gotten unlucky...
1 I could only imagine in expensive restaurants,
2. I am seriously surprised by, because while the person manning the train would almost always ignore you, so would everyone else - no matter what kind of gesture you do.
And 3... While I cannot fathom doing that on purpose myself, I'm extremely surprised anyone would bother interacting with anyone about that? Definitely doesn't reflect my experience living here for roughly 40 yrs
> include apps covering Japanese government services.
These exist?
Honestly asking, I've never been there myself so my only contact to their government is via social media, and the Japanese people can't stop talking about how you need to go there in person for everything and how absolutely nothing official is digital
Japan has a government ID card (MyNumber) with a digital certificate which can be scanned using NFC on your phone to log into do taxes online, check on your medical insurance details (like what charges have been made and your prescriptions), and pension information. It can also be scanned via NFC to apply for financial services like credit cards/bank accounts online.
> I would think making sure outside payment links aren’t scams will be more expensive than that because checking that once isn’t sufficient.
Ignoring the fact Apple isn't doing that anyway right now as others have pointed out:
There are multiple ways to make sure of that without it costing any significant money, eg hashing all scripts that are served on the link and making sure they're the same since review.
Not that they'd ever do the review to begin with, so the hashing won't be done either, but it's something that could be done on iOS/ipados.
And if you consider that infeasible, you might want to check out current CSP best practices, you might be surprised
It's not that simple. The EU may be the only ones to have codified that, but there's centuries of case law in other jurisdictions dealing with ownership, that once the matter hits litigation might turn out to say something other than these tech companies would like.
You say that as if I've got any control over the browser on the end users device, some of which will be configured to not apply these rules globally for accessibility reasons...
> your side effects (e.g. database writes) aren't idempotent
What does idempotent mean in this context, or did you mean atomic/rollback on error?
I'm confused because how could a database write be idempotent in Django? Maybe if it introduced a version on each entity and used that for crdt on writes? But that'd be a significant performance impact, as it couldn't just be a single write anymore, instead they'd have to do it via multiple round trips
In the context of background jobs idempotent means that if your job gets run for a second time (and it will get run for a second time at some point, they all do at-least-once delivery) there aren't any unfortunate side effects to that. Often that's just a case of checking if the relevant database updates have already been done, maybe not firing a push notification in cases of a repeated job.
If you need idempotent db writes, then use something like Temporal. You can't really blame Celery for not having that because that is not what Celery aims to be.
With Temporal, your activity logic still needs to ensure idempotency e.g. by checking if an event id / idempotency key exists in a table. It's still at-least-once delivery. Temporal does make it easy to mint an idempotency key by concatenating workflow run id and activity id, if you don't have a one provided client-side.
Temporal requires a lot more setup than setting up a Redis instance though. That's the only problem with it. And I find the Python API a bit more difficult to grasp. But otherwise a solid piece of technology.
In my experience async job idempotency is implemented as upserts. Insert all job outputs on the first run. Do (mostly) nothing on subsequent runs. Maybe increment a counter or timestamp.
Such a statement needs a citation, I don't believe you've got 20feet /6meter large trees being completely frozen like in the image of the article but I've never visited the area before.
I suspect you're just talking about small trees frozen over,which are indeed very common (1-3m). The habitat for trees being frozen like that just generally comes with strong winds all-year-round, which hampers their grows.
That's what made the Japanese ones special in the eyes of the people that were interviewed for this article - the gargantuan trees looking like monsters because of the size of the trees
> In the 1930s, we saw juhyo five to six metres [16-20ft] across," Yanagisawa says. "By the postwar decades, they were often two to three metres [7-10ft]. Since 2019, many are half a metre [1.6ft] or less. Some are barely columns."
> The cause is twofold, says Yanagisawa: a warming climate and a forest under attack. The host tree, Aomori todomatsu, suffered a moth outbreak in 2013 that stripped its needles. Bark beetles followed in 2015, boring into weakened trunks. Yamagata officials report that around 23,000 firs, about a fifth of the prefectural side's stands, have died. With fewer branches and leaves, there is little surface for snow and ice to cling to.
I found out about it because switching accounts isn't possible, you get logged into your old account unless some time has elapses.
Not a big security issue though, I mean after a day or so it it's actually logged out, just not within the same hour (no idea how long it actually takes - just know it's not within an hour)
reply