2h

thanks for your comment. I will make sure to never comment on a thread again, unless I am a world expert on the subject.

Its not my problem to solve, that's the whole point. Its a niche enough need that it shouldn't even be part of CSS. people who have a need for it, should figure out some solution on their own, not force their complication onto the entire spec itself.

I don't know the reason, but I don't like it. Nothing is wrong with that content, as you see its literally defined in the RFC.

this seems like something that should be left to end users to come up with a solution for. I would guess that a large percentage of web designers don't even know what this is, so adding it to the spec itself is just further bloating an already bloated spec.

one thing I like about the Go language team, is they are not afraid to say "no" to proposals. it seems W3 forgot this tactic, long, long ago, and just rubber stamp anything coming from the Chrome team. Sad.

I think it only impacts new accounts, because you can find older files on GitHub with that content. Not sure though.

Why cant universities fund it with their billion dollar endowments?

Code looks fine to me. Classic blame the programmer mentality. Shame on you.

> 6. i am not sure if this is correct. i am not basketball fan. i just google it.

why is AI talking like Kevin from the Office; why is AI "Googling" stuff?

I don't even understand what you're asking here, but it sounds like you're arguing against yourself, so please continue.

> Social networks could go hands off for moderation and allow plugable moderation engines that rely on domains for identity, trust, reputation

Every time this has been tried, it's failed miserably, as it should. People need to be able to post anonymously. Otherwise it's too easy to target the messenger, rather than the message. Think journalists, hackers, abuse victims, political dissidents, whistleblowers. Yes, this makes moderation harder. Sorry but that's life.

> 150 min/wk of aerobic exercise is the sweet spot (but push it to 40 if you can)

This doesn't make sense.

that fixed header takes up 21% of my viewport height. why do people do this?

exactly. people using milliseconds and calling it a unix timestamp are wrong. provably wrong. so for them to dig in, or anything other than say "oh you are right, sorry", is just a waste of everyone's time. Accept that you made a mistake, and move on.

here is some Go code that does the same thing:

    package unix
    
    import "time"
    
    // 2023-03-04 11:35:43.4859519 -0600 CST
    func unix_nano(nsec int64) string {
       return time.Unix(0, nsec).String()
    }

https://godocs.io/time#Unix

I fully support this. GitHub banned an account of mine with hundreds of stars, because they said I cannot have more than one free account:

https://docs.github.com/site-policy/github-terms/github-term...

but then other people said its allowed:

https://docs.github.com/account-and-profile/setting-up-and-m...

they also killed every issue, pull request and comment that I have ever made, across several years.

OK, now name at least two public servers that use that. I will wait...

> host name was leaked, but with SNI even that is gone

nope, you can still see it perfectly fine:

https://tlshello.agwa.name/

please don't spread misinformation.

Honestly I kind of dislike the security through scaring the userbase tactic. HTTPS is wonderful, but it is not needed in all situations. For your run of the mill static site, its essentially pointless.

Sure, if you are dealing with money or customer data, use all the crypto you want. But I think people should respect tools should be applied where they are actually needed, not just arbitrarily. You dont need a bulletproof safe to guard a stick of gum. Think critically people.

looks like it is closed source:

https://github.com/crul-oss

I would recommend avoiding making contributions on GitHub. If you want an account for search and whatnot fine, but I had an account with hundreds of stars killed. They said it was because I created a second account. I said they could delete the second account, or I would do it. They refused to accept this suggestion and are keeping both banned.

What's worse is they also kill every single issue, PR and comment you've ever posted. It's quite cruel and unnecessary.

wow. this is such a bad take, it makes me question using Age at all.

> tools should not have issues that need communicating to users, and if they did they should fix them, not delegate a choice to a user.

no tool is perfect, including Age. and no issue is fixed immediately, or at all. so instead of waiting months or years for an issue to be fixed, it can be quite helpful to throw a quick warning on the front page, so at least people are warned in the meantime. Its just a sign of respect, and of not wasting the users time.

> Imagine if every project came with a list of potential issues you have to form an opinion on

I would be glad if more projects included important to-dos or shortcomings up front, so that I dont have to discover them myself after a week or month of use. Further, no one is forcing users to form an opinion, or even read the known issues. you throw them in a section at the bottom the of README, then they can read if they want, and form and opinion if they want.

without doing this, you're essentially lying to the userbase, as you are aware of issues, perhaps even important ones, that are not fixed, and are purposefully hiding that information, or at least not being as forthcoming with it as you could be.

> VSCode has proved one could build hyperscale complex apps that perform well

did it though? It might perform "good enough", but its still an order of magnitude worse than native solutions. the only reason to ever use Electron or similar is for rapid prototyping. once you have an MVP, you should immediately work towards a native solution. people seem to forget that part, out of laziness or ignorance.

no Windows:

https://github.com/oven-sh/bun/issues/43

> Asciidoctor is actively overhauling its output I believe

It's been 9 years. That is not actively by any definition of the word.

> That looks like a minor issue in GitHub's stylesheet, not really an AsciiDoctor problem.

AsciiDoctor is adding p elements in places where it should not. GitHub could work around this error with CSS, but they have not done so, nor should they. It's a simple issue to fix, just emit the bare li elements.

I would caution anyone against using AsciiDoc. I really want to like AsciiDoc, but it has glaring issues for many years, that the developers seem to have no interest in fixing:

https://github.com/asciidoctor/asciidoctor/issues/1087

but not in the case. Things are not fine. I tried for years to bend over backward so that my code was POSIX compliant. At some point enough is enough.

Challenge accepted:

https://go.dev/tour/welcome/1

> on a Mac that has scroll bars that are invisible until you scroll

this has got to be one of the worst UX decisions of the past 10 years, come at me. You can just hear the meeting discussion:

A: make the scrollbars invisible until you scroll, that nets us 4% more width!

B: but it reduces discoverability by 50%, and its also an attack vector...

C: ship it!