I got permanently suspended for unauthorized activity but I’ve only ever browsed and commented.

And no one stole my 30 random character password with zero cross site duplication, either.

Only one of those begins with the letter K, so I’m guessing Kate Upton.

The NAS itself probably takes most of the power, which isnt logged. My server is a Raspberry Pi 5, so used 1.86kWh in September.

Not as of a few weeks ago

https://support.signal.org/hc/en-us/articles/11197884108826-Phone-Numberless-Registration-for-Android-beta

It needs to be Android with Google Play Services for the registration for a variety of payment related reasons, but they want to eventually remove that tie

I’m right there with you. Your comment gives me some confidence on this front to stage the upgrade this weekend.

A script checks container status and accessibility, and pushes a ntfy alert if it goes down. Healthchecks.io reports if the whole Pi goes down.

Also what I use on a Raspberry Pi 5.

Discord notifications also sometimes come with random delays because of Google bullshit, and ntfy supports UnifiedPush.

That looks very cool and maybe worth porting what I currently do — I just run a super simple template and each recipe is its own include file, with an auto generating index.

Even if the hosting dies the recipes are easy to read on github, and the network availability makes shopping easy if I decide I want to get ingredients for it at a store, or to share.

I’m not worried about some nebulous theft; the not sharing of a card number with a merchant is what I’m referring to.

I don’t use a phone case and it’s less secure besides.

I use Kagi too, it’s great.

The other commenter corrected your index note.

What I found most illuminating was a comment by the CEO in an interview, perhaps The Verge? The TLDR of it was that Google makes money when you dwell on their site (so they want the highest ad serves per search), and a paid search engine loses money every page they have to serve you (so they want to give you your answer fast).

So, the user and Google are at odds, and the user and Kagi have the same goal.

It’s tap to pay (or use the public transit) that’s keeping me back.

Why Molly over the official client, may I ask? The official client is already OSS.

I only read about that today, so I hadn’t even considered that angle. They’re doing some cool stuff in that space. jeff is the self-hostable one that does best as far as I know.

Both are reasonable, though I understand why Google is pushing back against it.

The assistant angle simply is saying that they have to expose APIs that they are already using and that they can’t lock away those features, especially on an open-source operating system.

On the second point, it’s just mitigating the first-mover advantage — just because Google existed before something else, potentially before an inventor-of-a-competitor was even born, doesn’t mean that they should be immune to competitive pressure.