slurp

Mull is fine if you use the divestos repo directly, but the f-droid version is behind

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.

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.

BIFL and Bluetooth are typically an impossible combo because Bluetooth means more batteries and electronics to break/be unreplaceable. Maybe modular systems will come in the future but they’d need to use a completely generic set of batteries.

My best suggestion, based on what you describe as your problem with wired headphones, is to get headphones with a removable cable, as those cables are generally pretty standard. I know sennheiser had a lock in mechanism but you can get third party cables. Also, I was able to take that out of my HD599s and use the headphones with a Bose cable.

Almost the same as my PC from 2014, which unfortunately is also my current PC. I had an asus mobo though.