I've said before, apple should just create a law enforcement mode that one can turn their air tags into. When in law enforcement mode, the tag will not report to your page, but law enforcement can go through legal channels to get the devices location.
To put a device into (or out of) law enforcement mode, can only be done over bluetooth (i.e. in proximity to device)./
There's a lot of funky protections (not encryption, which is well understood, but only "breakable" with leaked/extracted keys) for blurays and its beyond easy to sic AI on blurays and not just shortcut the protection mechanism or the like, but fully understand everything they are doing to remove it cleanly.
I was at redis when they changed the license (the first time). I begged the new leadership to not change the core license but to do a few things instead.
1) bundle the "source available" modules as part of redis source distribution
2) enable people who only want bsd code to be able to build a "redis_core"
3) commit to the community that the core will remain BSD licensed and that they are committed to making it the best key/value store.
4) increase the amount of source available code that until then had been kept closed (including what we called big redis/RedisOnFlash/MultiTier)
5) Require anyone using the redis trademarks in a commercial setting to ship the entire Redis (which includes the source available portions, so Amazon et al would no longer be able to use the Redis trademarks without a license deal.
Another alternative was to simply go to AGPL (which they went to anyways awhile later).
I failed to convince the leadership about this. I honestly think they squandered huge value in community engagement, but perhaps that's what they wanted. I left a bit after these changes were made as it became clear that the new US led leadership of the company wasn't particularity interested in what was the soul of redis. (previously was heavily Israeli led and a critical mass there was invested in redis as an open source product).
Funny story, the then new/current CEO used to be the head of WebEx at Cisco. We had a Q&A when he was hired and I asked, what did he learn from his time at WebEx about how to maintain market position (as they lost everything to zoom et al). His response at the time wasn't that convincing, but I was willing to give him the benefit of the doubt. I feel its fair to ask if the same thing occurred again.
> His response at the time wasn't that convincing, but I was willing to give him the benefit of the doubt. I feel its fair to ask if the same thing occurred again.
Business will have to try different things at different points due to external & internal pressures. Some decisions are reversible (at cost), some aren't. Decisions (chaotic / complex / complicated ones, at least) are not made merely based on available data and analysis, but also based on intuition, experiments, and predictions. Then, to look at the outcome rather than the process is missing the point. When the circumstance / situation isn't clear-cut, the feedback (the outcome of a decision) is in itself more valuable to the organization (than never having taken the decision, at all), especially when the costs (to reverse / change it) are bearable.
so there are a lot of words that I don't quite understand. basically decisions have to be made and perhaps they'll lead to bad outcomes, but having that outcome is better than not making any decision and one can always reverse the decision.
decisions that lose community can be reversed, but the consequence of those decisions (losing community) might not be reversible at any cost. Which it seems to be in this case.
As an example, at the company I switched to, they no longer use redis internally (not selling redis as a service, just using it as the internal caching layer of the product and never directly exposed to users, so would be a valid free use case under the switched to license) and instead use valkey.
While these use cases might never have made Redis Inc any significant amounts of money, they were free advertising that they gave up and even with the 2nd license change, is not something they've gained back as external contributors are more interested in valkey than redis.
And that goes to the email I wrote to leadership before the decision was publicized. 1) what are we trying to accomplish 2) what would be the negative consequence of the decision 3) is there another way to accomplish #1 while minimizing #2.
It was always clear to everyone that #2 would be a fork. Everyone already knew that Amazon was managing their own internal Redis repo where they did their own internal development and then would drop changes that they would benefit from not having to carry (vs Redis Inc doing a lot of their core redis work in public vs dropping completed things)
If #1 was to prevent Amazon et al from using redis trademarks, I don't think the license had to change. If #1 was to enable more non BSD code to be part of redis, I don't think the license of the core had to change. (how this would have impacted redis naming in linux distribution that only want to ship OSS code is a semi open Q but I think solvable).
Personally, I think keeping the core as BSD but including the the non BSD source available portions could have been an effective "trojan horse" for getting the community at large to be more invested in those pieces.
Also personally, I think what caused Redis Inc leadership to go down the path they did was Amazon cloning a non bsd source available redis module that Redis Inc published (RedisJson, to the point that they cloned the entire api including "easter eggs" that weren't really meant to be used, i.e. an API alias named after a (former) executive JSON DEL vs JSON FORGET named after former sales VP Jason Forget). That was the point of Amazon no longer playing nice in a competitive friendly way on the BSD code level, but to try to undermine how Redis Inc tried to distinguish themselves from just the BSD code. That's the right, but it perhaps caused Redis Inc to make bad decisions. (and as an aside, in today's day and age of AI, I wonder what protection these source available licenses have from AI oriented cloning).
the problem I've have with CD-Rs and DVD-Rs has nothing to do with scratching but due to degredation of the organic dye. I think this is less of an issue with BD-Rs, but I think BD-Rs can still cheap out and use the organic dyes.
do you think this makes the current government look competent? It's a terrible look for the current government when they are now found out to not be doing the job tasked to them in checking and enforcing agreements of who pilots are allowed to be.
Or to put it slightly differently. do you believe with this knowledge now out that they didn't do their job that it will drive more voters to the? While I can't predict how much it will hurt them, I can't imagine a world where it actually helps them. They failed again.
if I had to guess (not a user or employee of cloudflare).
1. dm-thin operates at 64kb block sizes, but many file systems operate at 4kb block sizes.
2. the point of skip_block_zeroing is to say if we write a 4kb fs block we don't have to zero out the rest of the 60kb dm-thin block (save performance).
why would one do this? perhaps the design was that one isn't exposing the raw block device to the container, only an ext4, xfs or the like fs. In those, the fs also knows what blocks are allocated and if you try to read an unallocated block will probably cheaply return you all 0s (why spend IO time reading something you already know is all 0s, similiar to a quick format).
Therefore, zeroing out the remaining 60kb is also just a waste of IO (ala not using quick format).
However, perhaps someone then decided to use the same provisioning mechanism to enable containers to have block devices (where one can now read the underlying content directly) and boom you have a problem.
or perhaps someone didn't realize the mismatch in dm-thin block size and page size that things are written at.
one thing I'll keep on beating the drum on is that microsoft missed an opening with windows 8. WinRT UI was great for mobile, but as noted desktop is different and they tried to force it onto it.
What we need (and to some extent we get in web, i.e. gmail is different based on resolution) is different UIs based on the interface one is using. a single app that can switch between UIs.
I strongly believe the lack of this is why convertibles have remained more of a gimmick than anything else, as in practice you either keep using the app the same way you always did as you switch usages or you use different apps in the the different usage scenarios because they are tailored to that specific usage scenario. Neither are things that really sell the convertible as something with strong usage.
The closest we've gotten is things like DeX on samsung and perhaps what google is rolling out with android.
when I worked at thomson reuters (and then bloomberg) they already did this had their own proprietary ratings of analysts to construct a weighted average for analysts reccomendations for stocks.
On this note, there is/was an apartment I'm semi looking at (in practice its just a bit out of my stretching ability) in my beach town that isn't quite first row to the sea, but one street back.
But the lot behind it (which would be across the street from the first row to the sea buildings has an empty lot that actually gives a decent sea view (through some hotels, but surprisingly not that blocked). so the question is why, is this lot empty? from my research it seems its not landing site for one of the major fiber networks and is built into an underground data center for the landing. So the assumption is that this is basically about as good as one can get that the lot wont be developed (at least in the semi near future) due to the difficulty of relocating the fiber and the security implications of building a residential building on top of it. Still just a bit out of my ability (which makes me a little sad) but cest la vie.
anyways just something I learned about the fiber optic networks that connect the world in my hunt for an apartment.
reply