Recent submissions

Comment · 4 months ago
Caught this one on may 10th, read last 3 sentences: https://imgur.com/a/oTr5Pcc

> You've provided the current rewritten thinking and the guidelines, but I don't see the "next thinking" content that I should be rewriting. Could you provide the next thinking that needs to be rewritten?

These sentences are completely unrelated to the actual conservation

Comment · 5 months ago
Github does not have a CEO
Comment · 7 months ago
Comment · 8 months ago
Comment · 8 months ago
> Something was lost by Arch becoming stable and not breaking regularly

...a smooth sea never made a skilled sailor

Comment · 11 months ago
Comment · 1 year ago
LlamaLab's Automate has a non-root privileged service via network adb service. Would it be possible to simplify app installation via adb the same way? An app that reads apk, sends it over pre-paired ADB. Sounds like a much simpler solution.
Comment · 1 year ago
Sequence does not cut it, since the op mentioned int indexed dictionaries. But yeah.
Comment · 1 year ago
from typing import Protocol, TypeVar

T_co = TypeVar("T_co", covariant=True)

class Indexable(Protocol[T_co]): def __getitem__(self, i: int) -> T_co: ...

def f(x: Indexable[str]) -> None: print(x[0])

I am failing to format it proprely here, but you get the idea.

Comment · 1 year ago
1) To quote myself: "I'm not saying email self hosting should not be done, I just say a bit of planning should be done". I self host my email. I just meant it is not "just rent a VPS and slap some docker containers on it"

2) I never said receiving email is a SPoF

3) Please explain in detail what do I do in order to keep receiving emails using "[email protected]" after johndoe.com gets undelegated. I do not know of a way and would very much like to know. If there is no way.. It is a SPoF.

edit: formatting

Comment · 1 year ago
So, now you have to worry about your VPS/Internet provider deplatforming you. Or about your domain name being seized. And spam filtration, backups, redundancy...

I'm not saying email self hosting should not be done, I just say a bit of planning should be done.

DNS seems like the most annoying part, it is SPoF by design. The problem can be mitigated, but seems like cannot be solved. For example, owning multiple domain names in multiple jurisdictions. And round-robin them. You cannot eliminate SPoF for any one specific service you want to login using email. But you won't lose access to everything at once.

Edit: P.s. At the same time, owning your domain for mail seems to be one of the most impactful things to do to reduce digital serfdom. Banned at *mail? Just switch those MX records and go on.

Comment · 1 year ago
There is - and was featured here a couple of times. atuin dot sh. But it uses sqlite under the hood afaik
Comment · 2 years ago
What may be the implications of a breach like this?

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton