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.
In first aid training one is told to be very careful regarding how you deploy an Epipen, since an accidental jab on an appendage (usually the thumb) is very bad news.
The reasoning I've heard is since Epinephrine constricts blood supply to the region and you can kill the tissue in an area with small blood vessels like your fingers.
Anyone aware of what the risks of a spray would be in similar contexts? I imagine stabbing a finger is not a risk here, but what about the spray getting anywhere other than the nose like in eyes etc....
EDIT: Looking at the product page https://ars-pharma.com/product/ it looks a lot like a Naloxone nasal spray so, I suppose its easier to position it in nose (not an inhaler like thing as I was imagining).
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?
If they can snoop on env vars of a running pod, it can snoop on the process. A k8s secret could be a file in the pod or a env var in the process, but neither are a persistent file distributed to developers
In effect, these are the same thing. If you try and deliver the software as a cloud service, you'll need to make the part that ties into your auth & observability stack, at the very least, open source.
Cloud companies are unlikely to be comfortable doing that.
> 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.
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?
The reason it won't really work for gamedev or complex software is that the risk of the business isn't really in the product-market fit, but rather in stellar execution.
If your business idea is dependent on being able to do a complicated thing, then a POC or a demo might make more sense for testing the waters and seeing if there's any technical impediment to the idea
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%