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.

I tried PCAPdroid recently and that seemed good

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.

The actual article says that the new thing is that it allows consumers to revoke access to information after the fact.

Personally I don’t mind initial registration, so long as they don’t continue to get data, so I’m not sure. There is some development for Garmin connectivity that I’m hoping comes to fruition.

I did like the old amazfit bip and that could be used without registration using the Notify for Amazfit & Zepp app, from what I can remember. I never used it with Gadgetbridge though, and it didn’t last for very long before dying (cheap build quality). It isn’t much of a fitness tracker either.

Look into Gadgetbridge, as that allows the bypass of proprietary apps for some trackers

Yeah, I absolutely want this option on all keyboards too. I just moved to openboard and it’s the thing I miss most by far.

The title here said E2EE is made impossible, I was simply saying that is untrue. Clarity matters. It says in the article they removed the bit about banning encryption or requiring back doors to it before it passed.

The rest sucks, as I acknowledged, and they want to make it easier to scan devices that would include messages that have been decrypted upon arrival. There's already spyware they does exactly that. However, that doesn't make it so that E2EE is impossible.

This is openly misleading. This sucks, sure, but it doesn't ban e2ee as the title suggests.