slurp

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.

Some Asian markets don’t use it, so there are some exceptions. This becomes important when the other requirements filter it down so much (but this was more of a problem a few years ago).

Sony is shifty with their PlayStation practices but their phones are genuinely good - seems like they are closer with the camera part of the business, which is pretty well liked from what I understand. The software support (or lack of) is the main issue but the hardware is clearly made by people that care (although apparently not enough about overheating on the IV series).

I miss my G6 a lot - easily the phone I was most happy with. Sadly, mine had battery issues years ago.

Why do I love the phones of (potentially) soon to be dying (phone divisions of) companies? I should ask a therapist.

As someone who just switched to an Xperia as it’s one of the few phones that still has a headphone jack, NFC, and microSD slot, this sucks. The software support is the biggest problem IMO because the rest is great.

No headphone jack is one potential catch

It’s very good but very expensive and the software support is not defined (but previous ones have been 2 years of security updates, which is terrible). I’m hoping Lineage OS will extend the usefulness or I may regret it. I couldn’t find another phone that had microSD and headphone jack that I wanted.

Sony Xperia 1V

I had that only when they got damaged, but they easily get damaged

I have had similar issues with USB-C ports but avoid wireless charging as it often causes damage to the battery via excess heating (particularly if not perfectly aligned). I’d give up a 3.5mm jack for a redundant USB-C.

There are but they are not reliable, even from reputable companies. I had both the ones I tried break very quickly, and moved back to requiring a headphone jack after that.

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

I loved Lego Island but will never forgive Lego Island 2 for the bad disk that would crash after 3/4 of the game. I never got to finish it.

Rock Raiders & Lego Loco were great (if a little inadvisable in terms of the Lego Loco letters).

This comment from A7pr8 seems to suggest it is possible to modify the apk via Lucky Patcher, which hopefully would then work on a non-rooted phone:

You can’t just send the app from your rooted device. When you mod the app on a rooted device only .odex file will be patched not the .apk file.

You need to rebuild .apk to be able to share it and the the other device should also has luckypatcher for it to work.

Simply when you patch an app use the option create modified .apk or rebuild it from “rebuild & install” in the bottom bar.

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.

I moved to Splid and found it a bit less clear than Splitwise but better in other ways once I’d figured it out. It’s not FOSS, unfortunately, but I do trust it much more than Splitwise.