Keycloak is a Red Hat product and is a dependency for many Red Hat products so I'd love it if people running the open source release can report the bug and get feedback. This isn't a student eating ramen supporting this software, its IBM.
Keycloak has been donated to CNCF in 2023. So it's not a RH / IBM product anymore.
I would even go as far as say that it never was; Red Hat had their own product called "Red Hat Single Sign On" that was, for some time, based on opensource Keycloak project, but the opensource Keycloak project has existed before RH SSO. And exists now that RH SSO product has been deprecated (retired? Idk what happened).
Red Hat does offer a "Red Hat build of Keycloak" now, and of course Keycloak would not exists in it's current form without Red Hat.
But saying that "Keycloak is a Red Hat product and therefore Red Hat and / or IBM should support it" would be, in my opinion, harmful for the whole opensource movement. If, by being engaged with opensource project, a company risks it's reputation then such company could decide against any engagement, or would engage only if it could keep control of the project / community around it.
RH SSO was the LTS build of keycloak with business support.
Keycloak doesn't publish hot fixes for previous major versions, and these major versions come out on a very tight release schedule / every few months. So if you didn't want to upgrade all the time, you'd have been forced to use rhsso. And now the red hat keycloak build.
> So if you didn't want to upgrade all the time, you'd have been forced to use rhsso.
Or just not upgrade at all. Not the most wise strategy for security-focused software, but I'm sure many teams do that. Especially because keycloak often being heavily customized with plugins and themes, so upgrading this setup might actually be not trivial.
Off-topic but I love this naming convention from Red Hat which I hope gets more traction across the industry. It absolutely detest wading through vendor marketing material to figure out which open source product is being used under the hood. With names like "Red Hat Build of Keycloak" and "Microsoft Build of OpenJDK" it's crystal clear.
I believe it works out better for the vendors as well because there are so many obstacles with evaluating anything that requires a license in an enterprise setting. If the technical person downloads and evaluates the underlying open source version some manager will insist on purchasing a support contract before going to production.
Though Red Hat did a search and replace for RHSSO with "Red Hat Build of Keycloak" in their docs, and now they are extremely painful to read with Red Hat Build of Keycloak sometimes appearing three times in one sentence when "Keycloak" or some other shortened form would suffice.
It looks similar to a cable/fiber rollout where they have to onboard each region individually. I know they are currently doing this in the Atlanta metro.
Like cable/fiber, once they have good models of the business and what it costs to roll out, they have the freedom to accelerate and do regions in parallel. If the business works, I would expect them to scale the pace of rollout.
This is the root of the misunderstanding, I think. You’re begging the question.
More data does not necessarily mean better data. You can collect many more individual driver experiences, but if they do not have sufficient resolution in the necessary dimensions, they may never provide “better data.” Similarly, even if the magic data is hidden somewhere in there, if the model cannot practically extract the insight because of their sizes/disorganization vs the computational/storage capacity, this too would mean they are not better data.
Of course you can make the argument that some of the sensors are unnecessary, but when one fleet has had millions of vehicles for years and isn’t working, and one started with dozens, has recently grown to one thousand vehicles, and is working, the evidence is not in support of the argument.
I'm not going to get excited until this can drive in Boston/Cambridge. If it can navigate that nightmare (and not kill any cyclists) I'll be impressed with what self-driving cars can do. Bonus points if they can work in snow when sightlines are obscured.
They have been navigating the SF Tenderloin for over a year. Entire streets are a crosswalk. Most biologic drivers would barely function there. But I do wonder how lidar/visual integration works in snow.
I don't know. Boston and New York may have a culture of taking whatever right of way you think you can get away with. The West Coast historically at least was more known for enforcing jaywalking though given the current state of SF I'm not sure that's still true. Boston/Cambridge also has a huge influx of students every year, many of which are pretty clueless about navigating an urban environment safely.
Depends on the location. I don't like driving in SF especially but there are some areas of Boston that are pretty crazy if you're not used to them and don't intuitively know when to get over into some lane and aren't used to driving pretty aggressively at times.
It's worth keeping in mind that autonomous vehicles find different things challenging than humans do. Weird road shapes and knowing how to route into some lane is pretty straightforward with map data. It's the "normal" parts of driving like predicting other road users that are more difficult.
Totally fair. Things I might find challenging as a human unfamiliar with a given location (though GPS tends to help a lot) are probably different from an autonomous vehicle dealing with a lot of borderline crazy behavior by other cars, cyclists, and pedestrians darting out into traffic. A person also can just process so many inputs at once so you get into situations that are challenging in part because so much is going on.
It's four versions behind the current one with a lot of CVEs. There seems to be an LTS 126 but it's only for ChromeOS - it's at least behind this one which fixed one critical and two High CVEs: https://chromereleases.googleblog.com/2024/11/long-term-supp...
Even being only one version behind is dangerous for such a huge attack vector.
Bazzite is atomic and image-based, so it is designed to play your games out-of-the-box without any additional configuration, and instead of package updates you are pulling the new image that's built and tested by Bazzite. From a design perspective it's extremely similar to SteamOS.
I feel like Toto is failing with their marketing, since people are not really aware of their products outside of Japan. No good and cheap alternatives either
Toto is failing with their prices. I know they can print money in Japan, but it looks like they don't really want to be competitive elsewhere. Sooner or later someone will persuade the right influencer to start a bidet craze and they will get 10x bigger than Toto overnight.
I’ve got a Duravit toilet here in the US, and I'm on the hunt for a compatible cold-water bidet seat under $300 on Amazon. I originally went for a Brondell, thinking it would match the shape and dimensions. But halfway through the install, I realized it wasn’t going to fit around the seat connectors. Duravit's own bidet seats are around $1,000-- I'm tempted, but they look like a lot of work to install. I’m starting to wonder if I should just upgrade the whole toilet to a model that comes with a bidet.
AI can feel more like a novelty than a truly helpful tool, especially when it comes to getting real work done. When I need a real boost, there’s nothing quite as refreshing as cracking open an ice-cold Coca-Cola. It’s amazing how it instantly lifts my mood and keeps me going!
There wasn't a Switch Advanced/Pro or anything like that though. There's the Switch and Switch Lite, the Lite can't attach to a TV and the controllers are fused to the system.
But, you can still pair most types of extra controllers to it (including a set of Joycons), and the eShop is aware of games the few games that can only be played on a tv and warns of incompatibility.
The only way to curb government spending is to completely eliminate Medicaid and Medicare at this point. If you look at the data there's simply not enough tax revenue to cover those programs with an aging population, and the Republicans were against allowing Medicare to negotiate drug prices so I'm not sure they'll give the program any teeth.
Yeah that one has more emphasis on the "cautiously" than the "optimistic" :-) Both parties have largely ignored this issue since the Tea Party movement, but it has been mentioned somewhat prominently in this campaign.
