• 1 Post
  • 179 Comments
Joined 3 years ago
cake
Cake day: January 13th, 2022

help-circle







  • It looks similar in structure to JSON:

    {
        "attr": {
            "size": "62091",
            "filename": "qBuUP9-OTfuzibt6PQX4-g.jpg",
            ...
        };
        "key": "Wa4AJWFldqRZjBozponbSLRZ",
         ...
    }
    

    So, it might be some JSON meta language. I just find it weird that it seems to contain all data, so you wouldn’t use this for validating or templating JSON.

    But ultimately, it also means with a handful of regex replacements, you could turn this particular file into JSON. Might make building your own parser almost trivial…



  • Normally, I would reply to the guy, because, you know, he’s a human being, but there’s so many replies, I doubt, he can actually read all of them and potentially someone else has already made that point.

    Anyways, I feel like something he kind of misses here is that many of us do it from a heartfelt place. Like, we’re all techies. We’ve all used commercial software to a point where we’ve grown so frustrated with it that we decided it is a waste of time.

    So, it’s not us saying “Why don’t you go and just have more time/money?”.
    Rather, it’s us saying “This thing is wasting your time? Here is a solution that I felt wasted less time in the long run.”.

    Yes, sometimes that does miss the mark, because not every complaint is looking for a solution. Or because we may be frustrated with restrictions of commercial software, which are not a problem for less techy people. Or even because we’re embedded in this tech world and are hoping to make it a better place, which someone just quickly visiting may not care about.

    But other times, I do just happen to know a lot about technology and a non-techy genuinely did not know about the solution I suggested and is actually really appreciative of me bringing it up. It does happen. And it’s not easy to discern who would appreciate a suggestion and who won’t.


  • And you wouldn’t have to reverse causality to travel backwards in time. You would just have to travel faster than the speed of light.

    If you can travel faster than the speed of light then you can arrive at a destination before you left.

    I know practically nothing about all the wormhole theories, because I just don’t consider them relevant, but from a logical standpoint, the above does not feel correct to me.

    The thing is, you would arrive at your destination before the light would arrive there from where you started. So, you could take out your telescope and potentially watch your own launch.

    But that doesn’t actually put you into the past. It just looks like it when looking into the direction you came from. Light from the other direction will look like you’ve fast-forwarded through time, because you now get more recent imagery.

    I don’t have another explanation why someone might think, this might put you into the past…


  • Hmm, but why do you think these things haven’t occurred yet?

    As far as I can tell, the speed of causality means things can have occurred in a certain location in the universe, but it takes time until the effects have permeated into the rest of the universe.

    So, it’s like a shockwave from an explosion. The explosion happens, but it takes a few seconds until you feel the shockwave.
    Well, with the difference that you can see an explosion before the shockwave. When we’re at the speed of causality, literally no evidence will have arrived in your position until it does.

    So, one could go meta-philosophical with basically “If a tree falls in a forest and no one has heard it yet, did it actually already happen?”, but yeah, I don’t think that’s terribly useful here.

    And well, if we treat it like a shockwave, let’s say you detonate some TNT and step through a wormhole to somewhere 20 km away. You would know that the shockwave will arrive soon, but does that matter? The shockwave will still just continue pushing on.

    And I guess, crucially, it did already happen, so you can’t do the usual time travel paradox of preventing that it would happen.


  • That’s actually not as obvious as it might sound. The thing is, as far as we know, light seems to have no mass¹. No mass means no inertia. So, if it accelerates at all, it should immediately be at infinite speed. But for some reason, it actually doesn’t go faster than what we typically call the speed of light. And we assume, that’s the case, because that’s actually the speed of causality.

    So, it’s reversed. It’s not that light is just the fastest thing and as a consequence of that, nothing can be transmitted faster. No, it’s actually that there appears to be a genuine universal speed limit and light would be going faster, if it could.

    ¹) Light is still affected by gravity, e.g. can’t escape from black holes. We do assume that gravity is just a ‘bend in spacetime’ because of that, meaning even any massless thing are affected by it, but yeah, we’re still struggling to understand what mass actually is then.


  • Well, I’m going to give the party-pooper response, even though science fiction and pop-science love to fantasize differently:

    The past and the future are theoretical concepts. They don’t actually exist in the sense that you can ‘send’ something to them.
    Obviously, you can write data to a hard drive and then read it out after a week has passed, but presumably that is not what you had in mind.

    But that’s also the essence of the time travel that the theory of general relativity allows. You can travel forwards more slowly along the time axis by travelling more quickly on the space axis (close to the speed of light), which means you might just need to spend 5 perceived years to end up in the year 2200.
    Similarly, you could take a hard drive onto this journey and it wouldn’t have fallen apart in that time.

    Travelling back in time makes no sense in general relativity. You would need to reverse causality for that, which is on an entirely different level from merely slowing causality down.

    General relativity would mathematically allow for the existence of wormholes, but that’s pushing the theory to extremes where it might simply not be applicable to reality anymore. We certainly have no actual evidence for wormholes.


  • Yeah, that is a valid opinion to hold. I am saying that trust is garbage.

    You could consider compiling the KeePass app yourself, if you’re worried about that one in particular.
    A guy I used to study with, decided that he just wouldn’t have a password manager on his phone.
    I’ve certainly considered switching to a Linux phone for that, among many other reasons…



  • I watched it on my phone in 1080p60 and the scale didn’t bother me. It’s not like I have to read a lot of text and the precise position of the player character is mostly irrelevant, too. Like, if you get hit by a train or something, the screen will flash red and you’ll react to it, too, so I’ll know what’s going on.

    Well, and I don’t look at the screen at all times anyways. 🙃

    Would like to see more of this journey…



  • This F-Droid-like model (also popularly implemented by Linux distributions) is usually considered an improvement in security.

    The thing with FOSS is that ideally you don’t have to trust the developer at all.
    In theory, you could read the entire source code and compile it yourself. Then you’d know for sure that no malware is included.

    Obviously, in practice, you can only hope that some nerds dig into the source code and notify journalists of malware-like behaviour.
    It is no perfect protection. But it is the only tangible protection that FOSS actually delivers.

    What does not protect you, is to trust each individual developer. They could publish innocous source code and then build the release binaries from a version with the malware-like behaviour patched in.

    But because you likely don’t want to compile each app yourself, you might still feel compelled to entrust that work to a third party. This is where the F-Droid team comes in. Rather than trusting each developer, you just have to trust a single team.

    Well, and if an app is built in a reproducible build, then even the work from the F-Droid team can be verified.