stagas

Very nice! And beautiful demo track also.

It shows all changes by polling the filesystem so there can be several agents touching it, yes.

That will repeat the `git diff` whereas livediff shows only the changes that happened now.

Dark Reader extension for Chrome.

Lack of comments is pretty big though for a human editable config.

I don’t know why this is happening to some clients. From SSL Labs test[0]:

SSL Report: textlog.cc

2604:a00:50:e3:216:3eff:fe34:8fc A+

192.64.84.165 A+

[0]: https://www.ssllabs.com/ssltest/analyze.html?d=textlog.cc

It’s early stage and we’re still figuring things out and how its final form should look like. Thanks for the feedback, it’s very valuable.

I see the retries. Sorry about that. I don’t know what going on, I’ve sent you an email with an invitation magic link from my personal gmail. It can be used within a week. Hope that gets delivered!

Re: timestamps, feel free to vote[0] on the matter!

Re: design, a lot of people seem to like it the defaults. If you make an account you can customize theme, color scheme, font face/size, and more. If we’re missing a more contrasty theme it should be easy to add.

[0]: https://textlog.cc/post/2326

Touché, yours got bounced, I checked, others’ are getting delivered. Funny how Resend doesn’t have a “resend” button in their UI. Just retry.

I’m not an expert on networking but that’s the verdict I get when pasting this problem to ChatGPT. We did have this and went away when we activated IPv6. Firefox and depending on your network/OS you might access the site via IPv6, in which case it will fail if it’s not accessible. I still have problem accessing it locally, curl fails, it works when I am in the network, so I don’t know what’s the case here. It works for some and not for others? Super weird.

Thanks! I think you meant to answer https://news.ycombinator.com/item?id=49425349 instead of this thread.

Might bring them back for historical posts, see: https://news.ycombinator.com/item?id=49425728

A solution here that I’m considering is revealing the historical information after a post has reached past a certain age. This will bring context to the post while also reduce bias on recent posts.

I do feel reluctancy answering to a post even a few hours ago thinking my answer might not be applicable to their context anymore. But not knowing, I believe keeps the conversation going for a while. I see it actually taking place.

So, what is the right thing to do here? More engagement and lack of information, or more information and less engagement? Not an easy answer.

Yes, your client is trying to connect using IPv6 and failing. This is odd however because we had this problem and then we’ve configured it properly and it was working. This must be some upstream issue from our hosting provider.

Edit: I’ve opened a ticket and waiting for their answer. Thanks for the report!

To resurrect old discussions. The hot algorithm makes old engaging posts stay a little bit longer, and with the timestamp it introduced bias that you might not want to answer a very old post. My instinct was right as users are engaging with those old posts more often now.

Oh we have it, that counter is still there, obviously that one is necessary. I removed everything that I considered noise and not contributing much.

I started textlog.cc as an experiment to see how far I can go without introducing JS. It turns out, pretty far! If you exclude the Web Push notifications which required a Service Worker script, all the rest is server-side rendered React. As a visitor, with all the hover cards and popovers you would think there is some JS going on, but it’s all HTML-only. I am enjoying very much the constraint and it hasn’t hindered any progress. It’s a proof a lot can be achieved by just HTML.

One of the reasons why I started textlog.cc, to slow things down, take our time and re-think what we want the internet to look like. It tries to be unconventional and against all of the engagement tactics that have enshittified every corner of the internet. Don’t lose hope, build what you want to see. That’s what I did.

And yes, we are still JS-free!

That’s cool, make sure I see it however on the onboarding screens. Big green switches (Proxy, Web Analytics) that I have to scroll through to get to the Ok so I can turn them off there.

It’s really not a lot per day that enter the top 10 to justify categories. You’ve browse them all in one scroll, around 30–50.

A simple screen when I did the switch that requires explicitly ‘Enable Proxy’ or ‘skip for now’ would have been enough. Also for ‘Enable Analytics’. None of these existed, or not very obvious otherwise I’d seen them.

I can’t recall if there was a setting to enable reverse proxy, if there was it was On by default since I didn’t expect to have reverse proxy enabled as well. But you can also rp without injecting a script. That’s overdoing it.

I just went and switched them to DNS only, they were on Proxy by default, that also should have been opt-in. Maybe I missed the option while switching the nameservers because I did it in a hurry but still.

No, I hadn’t enabled for any site. I had to enable first to turn it off.

Ok to turn this off you go Domains → Overview → your.site → DNS → Records → then Edit each entry to DNS Only (gray cloud). MITM gone now (I hope).

Oh gosh I didn’t enable anything like that also. I just wanted the nameservers in order to serve the bucket under my subdomain. What else is there I wonder?

Well, that would be a bot to show only what becomes no.1 but that would be too quiet of a feed.