Revered_Beard @ Revered_Beard @lemmy.world

Posts

0

Comments

21

Joined

2 yr. ago

From what I understood of the article, it's not just the size (which you can get from merging previous black holes), but the combination of size, speed, and angle that are raising eyebrows.

Smash two random black holes together, and the odds are, they're spinning at different random angles. Do that a bunch of times, and unless their angles all happened to be lined up just right, the the resulting spin will be a lot slower than the maximum speed a black hole of that size can spin. But these were spinning at 80% and 90% of their max speed.

Okay, so maybe they were both "normal sized" black holes that gobbled up a lot of matter around a galactic nucleus? That might work, except then you'd expect them to both be spinning in the same direction - but they weren't.

So, none of the scientists' predictions are really matching what they actually observed. Maybe it was one of those things, maybe those models are off a bit, or maybe there's another model to explain these kinds of black holes that we just haven't thought of yet.

TiddlyWiki might be a good option.

Thank you for taking the time to look into it!

Um... Yeah.... Using 3 gigs to store 19 megs of text is... suboptimal.

Maybe something neat will come out of this down the road, but right now it doesn't seem very practical.

tl;dr - By using this very strange file format, you can functionally have access to the vast power of a vector database, but with the local simplicity of sqlite.

If I'm understanding this correctly: if you wanted to do a simple search for exact text strings, and that was all that you needed, then yes, you should probably use something like an sqlite database to index and query from.

However, if you are working with massively large data sets, and you need a vector database (for contextual or semantic searches) - well, that's a next level tier of complexity. At that point, you need a vector database server.

What this thing does, however, is format your data into what they call "video" (but realistically would probably look like static if you were to actually play it in VLC). Then...

... I think it's hooking into some similarities between vector databases and video processing, and then using the mature video processing technology to process the "video" at lightning-fast speeds. And you get all of that contextual power without relying on a cloud-based vector database server.

(To be clear, I'm doing a lot of hand-waving over the "similarities between vector databases and video processing" here - perhaps somebody with a computer science degree, or an autistic savant, can explain why this works the way that it does.)

I think it's 100% a didgeridoo, but one that has been molded into a shape superficially resembling a saxophone.

As a longtime didg player, I can tell you that the thing that makes this absolutely worth every penny is not how light it is, the paint job, etc, but the fact that it can hit so many "hoot" notes (what they call "trumpets"), and that each hoot note is tuned to be in the same scale as the main drone.

Most didgeridoos have only one, or maybe two hoot notes, but I watched some other videos of these things being played, and I'm seeing four or five hoot notes, in addition to the main drone.

At that point, it's starting to grow beyond the realm of wind percussion instrument, into something that can play melodies.

I think you actually nailed the point perfectly. Part of the social contract is that an employer will provide enough money to meet the basic needs of the employees. When the employer fails to do that, employees can feel like "wage slaves", or prisoners, who are being mistreated.

"We've had to limit our food anyway," said Valdivia. "So basically you are kind of starving us, Kaiser."

I recently produced a radio drama on what life was life before we had child labor laws, and how they came about. If you're interested, it's called "Florence Kelley, The Children's Champion."

I think it's more accurate to say that a brain refusing to bring up a certain memory, is what makes it a repressed memory. "Recovering" a repressed memory can happen as part of trauma therapy, or it might happen by itself years later.

Trauma itself causes incredible changes in the brain, in some very non-intuitive ways. The brain has a number of different strategies for protecting the person, the "self", from unnecessary suffering, and it doesn't let go of those defense mechanisms until "it" feels safe to do so.

Honestly, out of all of the ways that the brain can respond to trauma, repressed memories is one of the simplest and easiest things to understand.

The fact that false memories can also be demonstrably created... Well, that muddies the waters a bit, it makes things more complicated to sort through, but it's entirely reasonable to assume that there is a mechanism for memory repression, and there's also a mechanism for creating false memories.

Ooohhh! You know what, I learned something new today! Thank you so much for taking the time to explain it in a way that made sense to me.

What I'm saying is those medical device companies just need to upgrade hardware. Not the user.

That is a valid perspective, but it doesn't take into account the burden on end users. Would you still feel that same way if you were the user, and the "update" required literal surgery on your body - not because the device failed, or expired, but simply because network standards have changed?

Because it's the cellphone equivalent of creating a pirate radio station, to put it in terms better understood.

Why not use the analogy of a Wi-Fi repeater or extender that can handle multiple Wi-Fi standards simultaneously?

For that matter, it should be rather simple to limit it to only "listen" for connections from known medical devices (though it's not like there are a bunch of 2G phones running around these days).

I'm listening, but so far, I haven't seen anything that explains why this would actually be a bad idea, or how it could cause any harm.

...you don't see the advantage in avoiding open heart surgery to replace an embedded medical device?

While I agree with you in principle, that's a hard sell to somebody with an embedded 2G medical device.

You don't want random companies making cell signal transceivers.

Setting "companies" aside, I don't see why it couldn't be some sort of DIY project. Like, a small computer with a both a 2G and 5G modem, a set of antennas for each, and some middleware...

In fact, there are some phones that support both networks... So why couldn't a spare phone be used? They technically already have all the hardware to make it work.

It sounds like there's a really big market opportunity for somebody to make a portable transceiver that converts 2G and 3G signals into 5G...

Additional info for the lazy: the name of the company is "Gravy Analytics", hence the name "Gravy Scanner" for this app. It's a large data broker, and they don't bother with pesky little details like "informed consent".

Anyway, they got hacked a month ago, and the hackers threatened to publicly release all the data.

https://slrpnk.net/post/17048112

Most likely, that means you're clean. On mine, the output is just a white screen with a list of the affected apps... Clicking on one of them takes me to that app's settings.

It does that one thing, with no explanations or instructions, so it wouldn't surprise me to learn that it doesn't show a message to indicate that nothing was found.

Is it? I just installed the Accrescent app store, and don't see it listed. It has 16 apps listed, including Accrescent itself.

Requirements:

About 300GB clear disk space for the entire planet. Probably an SSD unless you like pain, suffering and watching the slow creep of old age...

Lol, no kidding!

Jewel spiders!

For what it's worth: I counted about 85 or 86 "clicks" in 10 seconds. It's a loud click followed by a quieter click, like as if it's oscillating towards and away from you. The sound of the click itself is loudest at about 2.6 khz - whether that is simply the sound of friction, or some sort of electrical phenomenon, I don't know.

The fuzzy area at the bottom half of the spectrogram is the dull roar of distant wind. The clicks themselves show up as spikes, and the intense colors on the right are from where the voice starts speaking. The dark band above 10K is just the data lost from audio compression.

I can't imagine why they changed the name... (/s)

Looks like it should be available in the US in mid- to late 2024.