It may be an unpopular opinion, but I suspect treating juveniles with kid gloves all the time and the popularization of the view that they are entitled not be exposed to anything that may upset or offend them has lead to less personal resilience.
The social media environment does also mean that when subjected to bullying it is amplified by a massive factor that previous generations were not exposed to, so the change in expectations is certainly not the only factor at play here.
Yeah I think this is definitely a part of it. The average kid living in NYC a century or two ago was exposed to many more repulsive things on a daily basis than anything social media can come up with today. What's changed is that the expectation of "dealing with it" has evaporated.
Definitely used to be more common, but it wasn’t as if everyone was one of those things. My point was more that people were a bit tougher then, as they had more difficult everyday lives.
> The average kid living in NYC a century or two ago was exposed to many more repulsive things on a daily basis than anything social media can come up with today.
I don’t even need a citation here, I’m just curious what you’re imaging when you say this.
The amount of filth, trash, disease, and other unpleasant things used to be pretty crazy in NYC (and in other places like London or Paris, for that matter.)
Are you familiar with how squalid the conditions were for many people in the early 20th century? It was a whole lot worse than "trash in the street." More like, animals rotting in the street, ten people living in a studio apartment with no windows or fresh air, diseases widespread, people working 15 hour days in brutal conditions, etc.
As a user of Keycloak on a production project, I'm a little sad there is currently no support for opaque tokens.
Sure, you can treat the access token as an opaque token... but at the end of the day it could be a lot smaller.
We also experience a few front-end issues, like when a token expires, the browser tab goes back to the login page. If you leave the tab a while then press login, the token it is using will have expired. Rather than automatically retrieving a new token and posting the login again, the user gets an error message and has to authenticate again.
If you have two tabs in that state, you log one back in, switch to the other tab, if you refresh that tab, all is well, login proceeds automatically. If you press "login" instead, you get an error page telling you "already logged in" rather than just redirecting you back to the app... it also loses the redirect url so you have to press "back" instead.
Will see if we can fix these when we have time, it would be nice to contribute back.
gpg supports using public / private keypairs to encrypt any amount of data you like. I use it for uni-directional backups from machines where trust is an issue.
Or is the reality of this that it's just encrypting a symmetric key with the asymmetric cipher, and then encrypting data using that key?
Everything is encrypted with a symmetric key. It is just that sometimes there is an asymmetrically encrypted symmetric key packet included in the message so that GPG (or whatever) does not have to ask you for the symmetric key. This is all fairly generic, if you actually have the symmetric key you can use it directly even if a key packet exists. This means that you can give some entity a key to decrypt a particular message/file without revealing your asymmetric secret key associated with your identity.
Funnily enough based off Lenovo's reputation for their higher end laptops, in April I bought a Lenovo X1 Carbon Gen10, pretty much as they came out. The machine is a nightmare, and has been through about 10 firmware updates over the last 6 months, but has barely improved.
From day one and still now... on Win11 that it shipped with it won't hibernate, just a black screen on resume, then pot luck over the next boots whether it starts or not. Sometimes from shutdown it does the same thing. Under little load, it gets hot as hell, you literally can't type on it, I use a bluetooth keyboard. If I'm doing light dev work, 3h battery life, tops. Audio drivers are broken, the internal 3.5mm just emits noise above around 10% volume and is distorted below that. Shipped with an underpowered 45W adapter... same SKU now ships with a 65W (an i7-1260p w/32GB).
I don't think it's faulty, there are plenty of people with the same story about Gen10s. Mine is in for repair now, so we'll see, if it comes back with the same issues, it's getting warranty returned.
I know the X1 Carbon Gen9 is a really good machine, maybe Lenovo got screwed by Intel's 12th Gen platform and Microsoft's support for the processor, but the machine should not be going out the door like that.
Come to think of it... my XPS15 9560 from 2017 is STILL a better machine, which is what I switched back to while it's in for service (and cost half as much!)
The Gen 8/9 had a bad bios update sent out and set to install in the background.
It bricked the laptops it was installed on. I know this because I had to handle the warranty stuff for my coworker who was fortunately covered under their warranty.
Required a new motherboard and half a week of downtime, but at the same time Lenovo at least fixed the problem.
What scares the hell out of me, it would be so easy to backdoor an implementation of the open core in a well-hidden way.
Whereas the "big" CPU providers are staking their reputation and therefore future business on providing a non-backdoored CPU, it would be fairly trivial for an individual device manufacturer to provide a backdoored CPU design for their chip design.
It could become the whole cheap-device OEM firmware situation all over again (as we saw with many backdoored routers), but this time the blob is located on-die, so is significantly harder to reverse engineer or audit.
This is a problem with common thinking these days: " general belief that only some good guys have the keys". I paid for the device, I should get the keys!
If you care about security, you probably don't care about performance. High-performance cores are very complicated and hard to follow. But, if you give up performance, you can design a core that uses very simple concepts, making it hard to hide a backdoor in the design. Things like Chisel, which let you write your design in a higher-level language, help with that too.
My only annoyance with GitLab on that front is the lack of tags for "14.8-ce" to enable use of watchtower to keep the minor/security patch up to date, like we have on other images.
I definitely do not want to use "latest", in the past there have been updates or intervention required between major versions.
I will be interested to see how HTTP/3 fares on Virgin in the UK. I believe the Superhub 3 and Superhub 4 have UDP offload issues, so it's all dealt with by the CPU, meaning throughput is severely limited compared to the linespeed.
Waiting for Superhub 5 to be officially rolled out before upgrading here!
CPU on client or server? Client is probably negligible overhead while server is something that needs to be dealt with on an ISP level. Linespeed and latency live in different orders of magnitude to client CPU processing / rendering.
The social media environment does also mean that when subjected to bullying it is amplified by a massive factor that previous generations were not exposed to, so the change in expectations is certainly not the only factor at play here.