I’m more of a dust man, myself. It runs recursively so it’s easy to pinpoint the culprit.

[Image source: the project’s README]

I’ve heard that a lot of custom domains get filtered by tech giants. Have you experienced any problems like that? I agree it would be nice and self hosting it is pretty straightforward.

Like?

This offers no features over the embedded calendar in the mail app. Not even widgets.

What is an option then?

Oh that’s so cool! Thanks for the link.

When you say you host it live on Codeberg, do you mean something akin to GitHub pages? I didn’t know that existed

Of course! I’ve loved mine. The community and integration with Gadgetbridge are both awesome. You’re in for a treat if you go this route.

On the watch front I opted for the Bangle.JS 2. The abstraction to everything being JavaScript can be annoying, but takes away some foot guns for tinkerers who don’t want to optimize lower level code.

wherever you get your PCBs and associated components ;)

https://mikrophone.net/build.html

Cool video and channel. Thanks for posting!

TLDW:

[It was a cool attempt that may have spurred mobile Linux devs in an important way. Removable battery + hardware switches for communication subsystems were genuinely innovative and in tune with community interests. Also it was bad. 8 year old CPU, software that was trying to do everything everywhere all at once, cameras that didn’t work then technically did. Pine64 still exists and the Pinephone Pro is a thing (that the presenter hadn’t tested).]

Presenter was generous when describing the end product. It seems to me like they want to like it but came to the same conclusion as most did – it’s definitely not a daily driver. That said, it doesn’t have to be to remain a cool product.

Do give them a watch though if you have a chance. This is from a <1k subscriber channel and was well put together.

It’s mostly Mastodon. (Shoutout to @RmDebArc_5@sh.itjust.works for posting the link to FediDB)

I prefer Syncthing-fork for some more straightforward configuration. Mainly the three button options equating to “follow the run conditions, damnit”, “run damnit”, and “stop damnit”

If you want a device to do NFC payments you’ll need to look somewhere other than GrapheneOS. (Believe me, I’ve tried everything)

https://discuss.grapheneos.org/d/475-wallet-google-pay

Coarse Salt. Add just enough water to move it around + a little dish soap and shake. Works like a charm.

Amazing work! I’m very excited to see mobile Linux reach a usable state for every day processing. Thank your for your time and energy. It is valuable and going to good use.

Why the Pixel 3a? Is there anything special about it (or not special, which might mean my old 3XL is good for more than gathering dust?)

How can I get involved? I know my way around C and would love to pitch in.

Even faster – tailscale. For a cheeky way to play with your friends make a burner account with a shared login to get on the same tailnet for free. On the endpoints, turn off tailscale-ssh and any of their other “features” you don’t need.

GrapheneOS! I’ve been using it for a few years. Never going back.

Is this some Network Allowed problem that I’m too Network Not Allowed to understand?

Second this ^

I have one and it’s fine, but not directly supported by OpenWRT. Looks like Beryl and Slate are though