boarnoah

Ugh, that reminded me again that Firefox doesn't support HDR outside of OSX.

Although to be fair it is not like Windows in general supports HDR well for desktop use anyway, SDR colours are way too DIM like brightness is at 25%

I am slowly coming around to the idea of desk mics, like you I detest the idea of it hanging in my peripheral vision on the desk or monitor arms etc...

Even at the higher end of closed back headphones, there is a still a decent bit of noise leak.

I've Had V-Moda mic in the past, as well as Sennheiser and Beyerdynamic headsets with boom mics.

It usually isn't a problem with the relatively low volumes in a meeting, but any other time the noise leak is enough to get reliably picked up on recordings etc...

Something that gives me pause (to actually write into a blog) or to put up any toy projects / exploratory code as FOSS is I am not too keen on the idea of LLM companies and similar scraping that for their dataset [1].

Its not really a new problem, scraping the web and similar for monetary profit has been a thing for decades, but it feels worse in some ways? At least I certainly have paused and had more of a reluctance to making minor things available with no strings attached than I historically have been.

Same goes for writing into sites like HN or Reddit really.

Perhaps that is being selfish, after all there is some value in documenting things for other humans to find out about, maybe time-capsule of a blog is a better fit for this? Although blogging about anything particularly niche / context heavy is likely irrelevant a few years on.

EDIT:

[1] As in not help them even in a minuscule way, anymore than has already been done with them buying / scraping any public content already written.

> It might be a bit tasteless to be quoting ones own master's thesis

Eh, its something you poured a fairly significant portion of your life into?

You best brag about it whenever you get the chance :P

That doesn't cover what the GP was talking about with

> (i.e. if someone were to gain access to a running Kubernetes container)

right? Since those would still be secrets available in the env.

I get that if someone has access to read your envvars, its a foregone conclusion already (about how compromised you are).

However IIUC, the part of the point of doing things in memory with reading secrets (like with a Secrets Manager, is to eliminate having to keep secrets around as envvars/secret files in the runtime?

I'm confused, IIUC the AGPL can be simplified as "you can offer this software over the network, but like GPL the source must be available".

Whereas Elastic license is about, "you must not deliver this software over the network as a cloud service".

The things the Elastic license is trying to prevent seem very different to me?

The most interesting takeaway for me is:

> For studios or companies purchasing more than ten Unreal Subscription seats, Epic Direct Support will be available to purchase for an additional $1,500 per seat annually.

So ballpark that to a minimum yearly spend of about $18k in order to access the UDN (what is referred to there as Epic Direct Support)?

This is interesting since normally the terms for what it would cost to get UDN access are not public and instead requires you to reach out to Epic first.

Is there anywhere you have a written explanation of some of the features, especially in the paid version (love a good perpetual fallback license!)

Its really not clear what features like:

- "Performance/Load Testing"

- "Load Data from File for Collection Run"

etc..., are since there is no mention of those in either an upcoming features page or documentation.

Wonder about this myself, have noticed with folks like Rob Walling and presumably others. They all seem to suggest testing market fit by essentially doing this for features, and in some cases soft launching websites prior to having anything ready at all!

Seems risky if you are dipping your toes into something you do not have a deep understanding of the product market for.

Anecdotally I've seen with video games (the communities tends to be very vocal and somewhat centralized?), where inexperienced developers promise things that are realistically way beyond the capabilities, or promise things too early based on their honeymoon period for rough implementations. Then suffer on the other end when they fail to meet roadmaps or delivery of features at all.

It seems like an even worse situation with serious software with asks for larger amounts of money? Then again maybe this strategy can get away with it, because there is that lack of cohesive communities with some degree of group think who would get up in arms over bad promises?

I love the idea you folks are trying to get this upstreamed, would benefit everybody.

IIUC the reason HTML5 was dropped in the first place was for the big render re-work that went on during 4.27 + 5.0. So now seems like a good time to add modern WebGPU support back.

Do have to ask, isn't your business model for "theimmersiveweb" built around this WebGPU capability? Providing that tech to others or making your site a marketplace for web games?

Am I misunderstanding, there is a bunch of vSphere offerings on the list there, but surely they must still sell vSphere in some form to enterprises?

Isn't it still common to find as a significant part of most on-premise deployments?

It is extremely bizarre to advertise with typical Mixed Reality use cases (with display elements overlaid in your field of vision).

Is this actually true or do the people here who say "it lacks a display" mean something else? That it's not suitable for VR or non overlay applications?

This extension is still very cool.

+1 to Cyberchef, its awesome. If you really have qualms about the URL its trivial to re-host / serve it to yourself offline.

My favorite part is whole recipe feature (Cyberchef builds a URL with the configured processors you use to process data).

I find myself using that a ton to share XPath / JPAth expressions type work with sample data to others by sharing that URL.