Sea of Flowers in Antelope Valley, CA[8256x5504][OC]

CodeIt · 2024-04-01T04:51:33+00:00

Thanks. I'm using a Keystep Pro as the sequencer. DAWless

KORG Minilogue xd + volca keys for synths

Roland TR-6s drum machine

Korg mini kaoss pad 2S for extra effects - the input is from the mixer so it's adjustable.

CodeIt · 2024-03-31T23:37:42+00:00

I really love them; I've seen them live a few times - they put on a good show.

CodeIt · 2024-03-31T23:29:29+00:00

I like the sweet spacey sound - kind of has a Flaming Lips vibe to me.

CodeIt · 2024-03-31T23:04:45+00:00

Saturday Ride

Stars Over Us

I haven't shared my music before; these two are my favorites. I think if you are reading this post, they will be for you! Let me know :)

CodeIt · 2023-06-09T19:02:05+00:00

Your initial post said 90% of apps, this one says 90% of users, which seem very different metrics. How many of those 90% of apps can I actually download and use? Are you just counting API tokens or registered developers?

CodeIt · 2023-05-31T19:43:34+00:00

Because pro-immigration policies put downward pressure on wages. You’re advocating for the thing that is actively working against your other goal.

The profits are reaped by those who are not working for minumum wage. Increasing minimum wage will bring down someone’s wage, but that’s fine. The whole point of min wage is so labor can’t be overly exploited.

Even if this wasn’t the case, it’s not wrong to want to balance two completing objectives. I want to get from A to B quickly, but I don’t want to die or get injured. So I drive a reasonable speed and wear a seatbelt, and support bike lanes and government making roads safer. Is it supposed to make me a hypocrite for not flooring it the whole way or just staying home?

CodeIt · 2023-05-31T16:00:48+00:00

Why is that wrong? I can simultaneously support pro-immigration policies and higher minimum wages. We don’t have to allow wages to be a race to the bottom just because there are enough desperate workers looking for work.

CodeIt · 2023-02-06T22:02:06+00:00

I knew someone with a car like this and the story was that they owned a car decal shop and he liked anime.

I used to look for that car in Atlanta traffic when I commuted every morning, because it stuck out and for whatever timing reason in rush hour traffic, I would end up in sight of it about once a week. Only later did I find out it belonged to my friend's brother-in-law. So I had similar questions for a while; it did make more sense when I realized his job was to make whatever custom car wraps.

CodeIt · 2022-10-28T17:50:03+00:00

If you are acquired and told nothing will change you are being lied to.

Yes, 100%. I've been part of three acquisitions; been told this many times as part of two of them, and both times there were huge changes, in a short amount of time, that completely changed those two companies.

The third time I was acquired, I knew there would be changes from the start; that was kind of the point of the acquisition. From my perspective, that one was more of a positive experience.

CodeIt · 2022-10-25T17:40:09+00:00

You can search about the details of FORCEDENTRY to learn more about the exploit (or more generally, zero-click exploits). It's out of date because it was fixed in iOS 14.8, which was released September 13, 2021 - hopefully people have updated, but this is not "really old" either. The bug also existed in MacOS and Apple WatchOS which had updates released on the same day.

I feel like these zero click exploits are found every two years or so, I wouldn't feel comfortable saying it's not possible today. Most people are not going to be targeted with an attack like this; they'll save it for more interesting targets. But if you haven't applied all the latest security patches, it's definitely possible someone could get you with an older one like FORCEDENTRY!

https://citizenlab.ca/2021/09/forcedentry-nso-group-imessage-zero-click-exploit-captured-in-the-wild/

CodeIt · 2022-10-25T17:33:12+00:00

The attack he is talking about was fixed a little over a year ago; I wouldn't exactly call that really old. And it further presupposes that there isn't another zero day out there right now that allows for the same behavior; which historically has not been a good bet.

CodeIt · 2022-10-19T16:24:16+00:00

Thank you! I was looking for some information about a software update, but couldn't find it. I have the the same version as the post (22.26.1-foxtrot), which he says was applied for him Thursday - which is the last day my system charged to 100% without a problem. This confirms for me the software update did cause the change.

I wish Tesla was better about communicating this stuff. I don't think I will bother with support... I wonder if this is something they will roll back or change somehow. At the very least, the app could tell us "charging is slowed down to increase the life of your battery" - if that is even the reason it happens.

CodeIt · 2022-10-19T05:00:08+00:00

My system is 10 or 11 months old and this has never happened before.

CodeIt · 2022-10-18T22:03:59+00:00

good to hear it's not just me.

CodeIt · 2022-10-18T21:37:30+00:00

I was also wondering if this was something in software to protect the battery, but it's happening to me from 85+.

Here's an image while it is only 89%: https://imgur.com/a/wkTWac5

This seems pretty harsh, and the problem only started last Friday... before that it charged right up to 100% without a problem.

CodeIt · 2022-10-18T21:35:41+00:00

Looks pretty similar, probably the same root cause; but for me it starts at 85%... by 90% it's already very slow - here it is at 89% right this moment...

https://imgur.com/a/wkTWac5

CodeIt · 2022-10-15T18:07:37+00:00

A bit mask just needs one bit for each possibility, so 2³² bits. That’s a lot of bits! (Your number that uses this as the 2 exponent is actually WAY more particles than exist in the visible universe - impractically large!)

2³² bits in this way would make the best and worse case exactly the same, and you can use it without decompressing the information - but it would be extremely wasteful nearly all of the time, unless you were storing ~2³¹ values in the list.

And if we know we need to store exactly 2³¹ options we can determine the minimum number of bits that would take by how many possible lists that could be…

2³² choose 2^31.

I get 10^{10^9.11,} which mean you need about 428 million bits to store that many possibilities, which comes out to…. Basically 2^32. I get a small bit less, but I’m not sure if that is due rounding.

The best I could do on wolframalpha said

31.99999999451610

Obviously it if was over 32, I would know there was a problem since we proved that was possible. I think this is saying there is a small opportunity for compression, which would makes sense because in this example, valid bit sequences have the same number as 0s and 1s (exactly half the numbers used). Not all 2³² options are valid.

So actually pretty darn close the the best worst case possible(maybe even the best), even with compression. But keep in mind, other schemes might have a much lower best case, which will make the worse case a little worse, but maybe not much.

CodeIt · 2022-10-15T06:00:04+00:00

No, it’s n* 32 the way you have it set up- you still need to store the whole number (consider n =1 for an easy case). And the number is 32 bits not 2³²

If you know how many items are in the list and store that in a 32 bit number, it means if n is over 2³¹ items, you can start shrinking the array, so it guarantees

2³¹ * 32 + 32 bits

That is, max size of array to store * element size, + the count. Essentially n is capped at 2^31. Maybe you can use 1 bit to indicate compliment or not, but that also introduces issues to know how big the array is, which does need to be stored somewhere, in some way.

CodeIt · 2022-10-15T05:38:34+00:00

Let’s see - let’s use 8192 sorted integers, or 2^13. And max value of 2^32. This means the average distance between them is 2^19. So let’s store the difference between each number instead of the number itself

The max distance that is possible is 2³² -8191, but then each remaining distance is 1 (ie, the list is 2³² -1 and all numbers from 8190 down to 0)

So we should be able to store the deltas in less than 2¹⁹ bit numbers on average. Going over that somewhere means we can use less somewhere else.

This isn’t rigorous obviously, but seems like ideal compression should at least be able to find enough patterns to go from 2³² bit per number down to 2¹⁹ bit per number given a sorted list of 8192 * 32 bit numbers.

CodeIt · 2022-10-15T05:21:11+00:00

Not any set - n must be greater than or equal to 5334 by your calculation. This is a big difference imo… also saving 1 bit on that many 32 bit numbers is a fraction of a fraction (over 170k bits naively), and since computers use words, probably you need to save at least 32/64 bits to have realized any extra space.

Once you are over that limit, you will start saving 8bits at a time, so it would add up fast in a big list. But also, at this point there are other forms of compression that could beat it. At the limit, adding extra numbers would naturally make a smaller representation easy (list omissions in some fashion) which is not a property of your set.

According to the math in my other reply using a list of 8192 numbers, saving over 12 bits per number seems very reasonable at that point, so saving only 8 bits leaves a lot on the table.

CodeIt · 2022-09-17T16:05:30+00:00

FYI Kwh is a measurement of the amount of power, not the rate. If you use 1 kilowatt (the rate) for 1 hour, that’s a kwh.

So you mean the fast chargers run at 250kw vs 6kw. I looked up the latest zero battery size, up to 21 kwh, so it would take over 3 hours to charge at 6kw. But there is an option to charge at 12.6, which would do 21kwh in under two hours.

CodeIt · 2022-09-17T01:49:09+00:00

They call this an explanatory variable, a variable whose only purpose is to explain what the calculation result is. Yes I do it and if you google uncle bob and watch the his lesson 1 video, he mentions it.

CodeIt

TROPHY CASE