pull down to refresh

70 sats \ 6 replies \ @ek 6 May \ parent \ on: Stacker Saloon

To start with, your suggested solution should include the entire world in CC

write
compose
101 sats \ 5 replies \ @optimism 6 May

Mailing list?

PS: kind of dramatically self-important to seek the whole world as audience. Did you cure death?

reply
70 sats \ 4 replies \ @ek 6 May

Does this mailing list send all previously sent emails to new subscribers?

reply
25 sats \ 3 replies \ @optimism 6 May

I'm sure Claude can code you that feature in 2 minutes, but it sounds like a bit of an anti-feature. It's not really needed either - anyone can just serve an archive. Don't need centralization, don't need push on things that can be pulled.

Sure, Github is nice. Until it bans you. Or worse. Until it bans/suspends the author of the PR you just spent some hours on and the PR magically disappears, including your work. Or until it goes down or defunct.

If you disagree that GH is a weak link, fine. We can differ in opinions about that. All I'm saying is: it's just some software, and there can be other software. In 2026, we're only locked to those systems we choose to be locked to or that we don't care enough about to just spend some effort on to free ourselves of. This may change with the friction we experience from such software.

reply
70 sats \ 2 replies \ @ek 6 May

I don't disagree. I just think feature parity is a requirement for something to be a replacement.

reply
101 sats \ 1 reply \ @optimism 6 May

I think that that depends on whether you can pull off a process improvement by removing or reforming a feature, or you can trade a greater friction for a lesser one, or you decide to experience a different pain and discover what you really need.

reply
70 sats \ 0 replies \ @ek 6 May

Good points

reply