slurp

Ah, thanks for the answer, I’d missed this on the GH page. Unfortunately, that’s not what I’m after as I know I will end up with a complete mess of unusable notes or not use it at all if there are any stages of choosing a note type.

Ideally, I want version controlled, editable, searchable, taggable paper I don’t have to file away, which I can also type on and use other digital tools with (e.g for things like diagrams, spreadsheets). I haven’t seen anything particularly close to what I’m after yet but I’m hopeful that it’ll come eventually.

Is handwriting & drawing support planned?

The stars and planets, yes, but there is a lot of very diffuse gas that does collide

My personal idea/hope is that there is some other dimension of spacetime over which the big bang had directionality, emitting matter and antimatter across different poles, and that’s why. That’d also mean there’s an anti-universe, which is why I like the idea.

In terms of the galaxies, I believe there’s enough of an observable difference that I think we would be able to detect antimatter clusters, or similar, based on emission lines but I’m not 100% on that. Huge annihilation events from colliding galaxies and clusters would have massive energy signatures unlike anything else but the frequency of this would determine how likely it would be to see the evidence.

Oops responded to the wrong comment

deleted by creator

That’s what we genuinely don’t know. Based on the standard model, it should be in equal parts.

Glad I could help! I wasn’t sure if I was missing something in what you were trying to do - I get that in some cases folding in those features can make things a lot easier.

Don’t really understand why you’re overriding __new__. Surely it’d work better to use:

def __init__(self, source: str | Path, *args: Any) -> None:
        super().__init__(Path(source, *args).expanduser().resolve())

But this removes self.__source and the property. I’m not sure what the advantage of using that is but you could always set that before the line super().__init__(Path(source, *args).expanduser().resolve()).

EDIT: if I’ve completely misunderstood, please could you explain? I don’t really understand what subclassing is trying to achieve here, other than simplifying access to certain os.path functions.

Sounds like you were engaging in whataboutism and that was the problem

I’m with you on this. How on earth are one-off login events supposed to work? I want nothing about me logging on to be stored on that device or account other than, for example, the code I download. Maybe I’m missing something but the search I just did suggested connecting my phone via bluetooth, which is also not an option.