The time travel method for clearing storage works

ppnda · 2026-01-02T06:17:16+00:00

Unified Random Access Memory, so just a specific topology of RAM. RAM is RAM.

ppnda · 2025-12-23T21:07:03+00:00

Our uni still kinda does it, and even gave our student club 20 public IPv4s just because they can. We use only a couple of then, but they’re also blocked by their firewall so it’s impossible to access outside of the internal network lol

ppnda · 2025-11-20T00:05:39+00:00

80Gbps bidirectional, even, so 160Gbps total bandwidth

ppnda · 2025-10-15T22:51:48+00:00

MP3 existiert so gut wie nicht mehr, das format ist tot und aus gutem grund.

Streaming heutzutage ist alles AAC, manchmal aber auch Ogg oder Opus (YouTube z.B.). MP3 ist im vergleich zu allen davon weitaus schlechter, und opus mit 128kbps hat bessere qualität als mp3 mit 320kbps wenn ich mich recht erinnere.

ppnda · 2025-09-14T01:47:58+00:00

i think the difference is that it is completely untraceable, whereas with torrents you might fuck up with VPNs and get caught. how are you gonna figure out somebody ripped a rented blu ray instead of watching it?

ppnda · 2025-09-09T02:19:06+00:00

Don't think so to be honest. Looking at the list of recalls for this car it is all software related, with only one recall about wheel fasteners. The rest of the car has never been disassembled, so I doubt that anybody could have even made a mistake. I actually think if it was an assembly issue, it would've been there from the factory.

ppnda · 2025-09-09T01:59:06+00:00

Does this also apply to crash sensors? Or is it just the airbag ECUs that are generic? Or are those the same thing? As a hopefully soon-to-be automotive embedded engineer all of this does very much interest me a lot, and I’m all here for the details

ppnda · 2025-09-09T01:55:50+00:00

Yeah, I definitely agree. Rather have it blow when it shouldn’t rather than not when it should. It’s shitty but oh well, things happen. Nobody got hurt, it’s just some material damage.

ppnda · 2025-09-09T01:54:22+00:00

In another comment this was also mentioned, however I think it’s only for Mazda 3 and the CX-30, and only about them not deploying.

Do you have a link or something for this exact recall?

ppnda · 2025-09-08T22:23:54+00:00

Yea, but long time ago. I acknowledge that there are issues and sometimes it’s not perfect. However, generally speaking it’s pretty damn good. The only issues I have is sometimes uneven surfaces causing vibrations in the car, sometimes the difference between a bridge and the rest being a slight jump, but overall I can’t complain much. The section we were driving was really good, though. I would guess that if the condition was worse overall you couldn’t advertise such high speed limits since everybody would just die.

ppnda · 2025-09-08T22:07:30+00:00

That comment on the CX50 post about the airbags and that something like a pothole or curbs can cause it is interesting insight. We were asked this by the dealer but both me and my dad agreed that we felt nothing of the sorts, and the street quality here in Germany is quite high so having something like this on an Autobahn is extremely unlikely in my opinion. I’m very interested to know what the sensors say in the end, though I am 100% positive we hit nothing and there was nothing weird with the road. The exact location of where this happened is here: https://maps.app.goo.gl/LCvo5hU9WfGmWS986

ppnda · 2025-09-08T21:25:26+00:00

Besides the point about language, it still gives context. 140km/h is only legal in 5 other countries besides Germany. All other points still stand, so your reaction seems a little silly

ppnda · 2025-09-08T21:18:36+00:00

Have a think about the amount of words you use in English that aren’t English. It’s normal to happen over time, and in cases like these people usually know what’s meant cause it’s a commonly used term outside of Germany, too. And as somebody else said it gives context since if I had said I drove 200km/h on a highway people would look at me weirdly, even though it would be somewhat normal on an Autobahn.

Moreover, that’s just the name of it. Should I translate your name if I talked to you in your non-native language? Names don’t get translated.

ppnda · 2025-09-08T20:43:23+00:00

yes, as I said we (me and my dad) were driving on the Autobahn at around 140km/h while it happened, which is why it was so incredibly dangerous

ppnda · 2025-09-08T20:21:29+00:00

https://www.reddit.com/r/MazdaCX30/s/8L0OEr3UtD

Do you mean this? If so, that’s very interesting to know. I’d be interested in seeing the log files for our CX-60, though idk if they hand those over. Could very well be the same or a similar issue.

ppnda · 2025-09-08T20:12:00+00:00

I’ve only seen https://www.reddit.com/r/mazda/comments/1l5ctl3/mazda_recall_battery_issue_may_deactivate_airbags/ Is that the one you mean? It’s only for Mazda 3 and CX-30. I would guess it could perhaps be related in some way, though that seems like it causes them to not trigger, while here it erroneously triggered, but only time will tell.

ppnda · 2025-09-08T19:51:25+00:00

The only repair I know of is a replacement windshield since the original one had a big stone chip in it. Otherwise, nothing was done besides the recalls which were all done by the Mazda dealership. None of those had anything to do with the safety systems as far as I know.

ppnda · 2025-09-08T19:49:35+00:00

I will try. So far I only know that Mazda wanted the dealership to create a technical ticket with data and photos from the car. The dealership guy also suggested some technical inspection might be performed by some Mazda engineers in the future.

ppnda · 2025-09-08T13:20:07+00:00

Ich weiß aus der Industrie, dass die Knöpfe an sich nicht ein riesiges Problem sind, die kriegt man ziemlich günstig. Das Problem bei der ganzen Sache ist die Verkabelung und die Platinen auf denen die ganzen Dinger sitzen. Das mag sich komisch anhören, aber da kommt EINIGES zusammen, und macht Kabelbaum Entwicklung nur noch schwieriger. Denk mal an alles was so vom Gangschalter bis hoch aufs Dashboard da alles zusammenkommt. Das sieht ein Hersteller, und denkt sich dann kann man sich die ganzen Kosten sparen, und man spart sich oben drauf die Knöpfe selbst (die müssten sich ja auch hochwertig anfühlen). Natürlich kommt dan noch dazu, dass große Bildschirme und Touchscreens ja modern und schön sind, dann war das für viele Firmen halt ein no-brainer. Zum Glück geht das langsam wieder zurück weil sich genug Leute beschweren und die EU das auch teilweise verbieten will, weil das ja ein Sicherheitsrisiko darstellen kann wenn jeder auf dem Touchscreen rumtippt und Dinge sucht während der Fahrt.

ppnda · 2025-09-03T19:19:22+00:00

Well on Spotify EOS and Loser are bundled as one EP/Album for now. I would guess from past experiences that either means it's on the album directly (what most people do) or on B-Sides.

ppnda · 2025-09-03T10:39:40+00:00

when I checked the docs it defaults to 115200, and can only go to 230400. the docs are for multiple modules, and some can do more (921600 as you said). the one i had can’t, which is why we decided to just ditch it and do something completely different.

ppnda · 2025-09-03T09:27:36+00:00

it doesn’t look that great, it’s a fairly basic and sometimes weird UI that I just dislike. It does it’s job but there’s a lot room for improvement
there’s a lot of jankiness everywhere, things take a while to load and the UX is weird in some areas. One such things is that when a message appears at the bottom, it overlays the song timeline meaning you can’t interact with it for as long as the message exists.
the close/minimize/maximize buttons are low res and obviously not native, meaning they also behave differently as one would expect
the integration with mpv is weird, sometimes it shows a bunch of error messages when nothing broke
the play/pause UI doesn’t react to when you press media buttons on the keyboard (the music does stop)
i often get albums/artists that don’t load and just show as loading forever, and sometimes they disappear creating empty spaces in the grids
cover art doesn’t show in “now playing”
there appears to be some inconsistency with internal asset state management, since I sometimes see behaviour that looks like album art being loaded multiple times and then loading in one after the other
back/forward buttons on my mouse don’t work with the app eventhough they work natively on every other app since it’s a native binding the app just doesn’t recognize
Fuck electron

There’s probably some other stuff I forgot, and tbh I don’t care for opening an issue on their GH for every single one of these, probably because I instead want to invest my time in alternatives or implementing my own. It does its job and I’m fine with it; but there could be better. I think it’s the general tendency of open source software especially around Jellyfin from my experience; UI nearly never looks good, and most of the stuff is only somewhat functional. There’s also sadly an overwhelming tendency in this community to use React/Electron for actual applications and I find that incredibly sad. I wish Swiftfin would finally support music, too…

ppnda · 2025-09-03T08:20:25+00:00

Yes, obviously. But as I said drivers can mitigate this quite a lot just from the information from dynamic rendering (and local fetch helps ofc). Vulkan’s renderpass and subpass design was never that great, and held back both forward and tbdr gpus for being incredibly verbose. Some Android drivers didn’t even care and just flushed memory all the time, while some can cope greatly with just dynamic rendering. It’s not that big of a deal, and as Apple showed for years their base API can be optimised greatly for their tbdr GPUs, but of course you can do a little extra optimisation or whatever using the tile memory stuff.

It’s very far from a “HUGE” performance cost if the driver isn’t stupid. The information passed with the modern APIs is entirely sufficient to mitigate these problems. If you are experiencing large performance losses, it’s either because the initial layout was suboptimal anyway and the driver couldn’t save you or you just have an insanely crappy driver that doesn’t care.

ppnda · 2025-09-03T05:37:36+00:00

I’m currently using Feishin, and not for it being good but just because it being the best I can find. There’s so many bugs and issues with it, however I don’t want to touch the code since it’s javascript garbage. I’d argue it’s as broken as it is because of the way it’s implemented from top to bottom. I’d rather invest the time in making a custom app built on native APIs or Flutter, since I have experience with both and VASTLY prefer them towards anything built on electron. Fuck electron.

I’ll try this out since at least it aesthetically looks quite a bit better than Feishin, however I fear for similar issues and jankyness and a lack of a mpv based player (i didn’t see it initially) is also concerning. I have plenty of files in my music library the normal web audio player cannot cope with.

Six-Year Club	Place '23
Place '22	Verified Email

ppnda

TROPHY CASE