![](/static/253f0d9/assets/icons/icon-96x96.png)
![](https://media.kbin.social/media/7b/56/7b56e489f96f7c0deba67d7ef39731267c3c3c1f8c5d87ad37480fa9b74892d6.png)
Sure, but the algorithms themselves will have to be provided by the instance, so I guess different instance might make different choices, for example due to privacy concerns etc.
Sure, but the algorithms themselves will have to be provided by the instance, so I guess different instance might make different choices, for example due to privacy concerns etc.
Sorting by new also is an algorithm.
Not trolling here: I think this is something the fediverse will need to decide at some point. What are the acceptance criteria for timeline presentations? But this would also be a perfect example of diversity: don’t like the way our instance sorts your timeline? No problem, here’s some instances that do it differently.
But hey, someone’s gotta do it
When the going gets tough, the tough get going
Yeah, and just googling something will be completely useless with a project named after a famous rock musician.
„How to upload pictures lemmy“, yes, thank you google, I know how Lemmy Kilmister looks, thank you.
That’s (among other things) why I hope kbin will be the victor of that race…
Lol, this community is simply amazing already :D
Somebody just reverse-engineered the App and the files’ encryption and poured it into a simply python script, see the comments in this thread.
:O Wow.
That is just simply amazing. Can confirm it works.
The file names are always the same, prefix and the sounds name, e.g. if the sound is called “The Electric Forest” it’s com.HolographicAudioTheater.Naturespace.TheElectricForest.
I guess I could write a scraper and parse the whole collection.
Well, thank you kind stranger on the internet.
Ha, I was just writing an update when your comment came.
I followed your advice and installed mitmproxy (basically fiddler2 but open source), which was easy enough, and managed to find that the app just posts GET requests the homepage, which result in a 302 Temporarily Moved, which ends on a public S3 folder.
The GET request includes some “ID”, which I’m not sure I should post publicly, maybe it might identify me? It’s like:
GET http://www.naturespace.com/ns5ios/?command=download&path=%2Fmedia%2Fmodules%2Fcom.HolographicAudioTheater.Naturespace.Aegir&lang=en&id=REDACTED&bvrs=5.15&sysv=16.5&model=iPhone&bid=com.HolographicAudioTheater.Naturespace&sys=iOS&loc=en_DE HTTP/1.1
But yes, it seems the files are encrypted. I couldn’t find anything to open them, and no file identifier knows what it is. If you manage to get somewhere, that’d be awesome, my tech knowledge definitely ends here lol.
I guess it’s not actually illegal to post this, since it really is just a public folder, so if anyone els wants to look at it, here’s a file.
Ah, thank you! See, it didn’t even occur to me to just intercept the audio in transit. That’s really helpful, I will try this, thank you very much :)
Yes, I thought about that as well, but if possible I would prefer to retain the original data (also I just like to tinker with stuff :) ).
However, like you said, they’re doing some “spatial” stuff they don’t disclose. I assume it’s just some EQ, but if they really have some algorithm to compute HRTF or even they’re own audio format, then re-recording might actually be the only solution.
The information posted is completely outdated, Germany has changed its laws considerably since then:
This is old and false information. The incident in the link happened already a decade ago and laws have changed since then.
The current situation is that they need to prove it was you and not someone else in front of a court, so if you tell them it wasn’t you but someone you know they’d need to open up a court case which is way to expensive for them and that’s it.
Also what are you on about „citizens reporting on each other“, lol. This is some lawyers who found an easy way to make money. Those exist in every country. Also everywhere „private companies“ (aka lawyers) can make investigations and go prosecute someone. That’s what they’re for.
Not for very long, but not for the reasons countless sci-fi movies and shows have told you: you’ll neither explode nor freeze to death.
People think of vacuum as something massive, but it’s actually just 1 bar difference.
Atmospheric pressure is (roughly) 1 bar, which is comparable to 10 m of water. So getting put in a vacuum is like ascending from a 10 m dive.
You don’t implode at 10 m depth, and you also don’t swell up on Mount Everest, which is roughly at 0.3 bar.
The biggest threat to your life is the actual decompression.
If you’re abruptly thrown into the vacuum, and you don’t manage to exhale immediately, the air in your lungs will expand and rip your lungs. Which is one of the biggest dangers of diving.
But more likely is that it‘ll just rip the air out of your body, which probably isn’t good for either your lungs nor your intestines.
You won’t freeze to death, because there’s no medium to transport the energy away, so you’ll only lose heat through the actual radiation, which takes pretty long. Much longer than in cold water, anyway.
Also, your blood won’t boil, since it’s protected by the skin. Maybe the exposed areas, your eyes, your saliva.
So, if you survive the initial decompression, your chances aren’t that bad, after all.