KajMagnus

https://github.com/tanrax/org-social-host

If you don't update your social.org at least once a month, you will lose the domain and the nickname will be released

I usually don't post once a month. Nickname released, that's a security problem.

Looks as if: org-social.org is a single point of failure? Hmm

I wonder if there's ways to solve those problems. Maybe you'd end up w sth like AT Proto in the end

Interesting to read!

contributions

One thing I think you and the other "AI math builders" have done, is to show how good the top models are at logics and reasoning.

I didn't realize how good they are, until they solved an Erdös problem. And now lots of Erdös problems!

(Plus verified that the AIs actually did solve the problems, that's not easy :- ))

no one cares about forums anymore so trying to innovate in the space is a waste of time

Not sure about that. To me it looks as if Facebook is self sabotaging, for example their local events page is broken and has been for years. FB-the-company seems defunct internally, and if they start fading away (slowly over many 10s of years), maybe forums will make a comeback (slowly). Also, if AIs destroy Reddit, this might be an opportunity for smaller forums that have ways to block boring AIs.

Any feature you can think of has probably been implemented by someone at some point

Definitely not :- )

That's how GitHub discussion works :- ) (or did you know?)

Look here: https://github.com/jj-vcs/jj/discussions/ — by default, sorted by last activity. But you can also sort by newest, or by votes.

For comment threads, look at e.g.: https://github.com/jj-vcs/jj/discussions/5509?sort=old — sorted by time, by default. But you can also sort by upvotes.

***

The forum software I'm developing, https://www.Talkyard.io, is also threaded, and can sort by time or by votes. (Both discussion topics and replies.)

F.ex. go here: https://forum.talkyard.io/-9qb49/solving-problem-first-comme... and scroll down to the replies section and click `Oldest first` to change order.

In addition to oldest/newest/"best", you can sort top level comments by time descending, and deeper comments by time _ascending_ or by votes — creating a kind of "micro blog feed" where each top level comment is the most recent "micro blog post" — but replies don't have to share the same sort order. "Newest, then popular" and "Newest, then oldest" I call these sort orders.

Also click the "Recent posts" in the upper right corner, to see the most recent comments sorted by time descending.

***

Anyway. There's people who think the hybrid approach you mentioned is an good idea.

You can also have a tree view side-by-side with a flat view — see this comment (in this discussion): https://news.ycombinator.com/item?id=48770861

If you click a comment in the flat view, the tree view jumps to that comment, so you can see it in its context.

You can have a chronologically sorted tree view

Couldn't that be a change-sort-order-button? But this doesn't solve the find-the-most-recent-comments problem?

Is there any reason why flat/tree view could not be toggleable

I actually implemented both flat & tree view in Talkyard (forum softw I'm developing).

Not toggleable, but side-by side, so you see the threaded discussion in the middle, and comments by time descending in a sidebar.

See: (incl demo video)

https://forum.talkyard.io/-32/how-hacker-news-can-be-improve...

(Old HN discussion: https://news.ycombinator.com/item?id=12663844, but blog link broken (seems I let the domain expire))

I think they meant that different people can give you different and conflicting advice.

Also, check out the Goomba fallacy. (The way you wrote "the advice was... now it is...")

Yes I guess there exists such blog posts. And that it varies from person to person of course (what they already know or dont).

This blog post in particular though, I got so bored so I couldn't finish reading it. I gave it another quick try now because of your comment :-)

was AI, but it was interesting nonetheless

I suspect the prompt given to the AI was 3 sentences, maybe interesting sentences,

and everything else was AI expanded, a waste of everyone's time? (Those who read everything)

Interesting, didn't know about that Github functionality.

I'd like to not depend that much on Github, and instead I'm thinking about having some kind of archival repo where noisy boring historical stuff can be saved (but I'd delete the branches in the main repo). Or renaming historical branches, eg adding an "old/" prefix.

That's interesting, so you keep the branches from before the squash -- but do you also rename them somehow, to show that they're now "frozen historic versions"?

The whole website was apparently AI generated 3 days ago [0], leaves me wondering if this is partly a HN bots upvotes manipulation experiment. Or people here really think an AI gend docs website is top news nowadays? Has the HN demographics changed

When the website is AI generated anyway, why not ask Claude or Gemini directly instead of going to the specs website?

(Maybe it's useful to the author himself, but personally I don't have any reasons to trust the website more than asking an AI myself + asking for references)

[0] https://github.com/jdevalk/specification.website/commit/d8ec...

I think the AIs don't have enough information about the problem. There's many things those who wrote the prompts forgot to mention. And some of it maybe is tacit knowledge?

Then, it doesn't matter if you add 1000 frontier models -- they still can't generate a good report.

But yes I suppose you can get rid of hallucinated citations though

Top 18%! I denied everything, unless I could see at a glance that it was safe (like Git diff)

Aren't you overlooking the main point of the article?, the reason they migrated:

concurrency — eliminating data races essentially, which we had before. Really gnarly bugs

this is the one teams report most enthusiastically. The classes of bugs that survive go test -race and reach production (data races, nil dereferences, missed error paths) just don’t compile in Rust. Oncall rotations are typically very boring after a Rust migration. ...

I hadn’t had to chase down a crash, or some weird multi-threaded race condition, or some of these other things which actually consumed a huge amount of my time before.

(They say at InfluxDb)

That's not a Rust vs. Go slapfight? Instead, sounds like a good judgement to me

There's no metrics or KPIs that encourage more AI use? (In his team?)

(I guess you would have mentioned already)

Saying the model failed to write a competitive C compiler makes more sense.

I don't think they tried to do that though.

today's models are not yet able to produce production software without close supervision, even when uncharacteristically good specs and hand-written tests exist.

That's a good point anyway

Or when you find some old source code at your workplace, and you're like: "this looks pretty nice, I wonder who wrote this?"

Check out Qubes OS and vault VMs and (I haven't started using yet) split SSH / GPG.

If a package developer maliciously breaks everyone's builds,

isn't that pretty great?

Because now you have learnt that you can't trust them

How do you know the hash in advance?

My impression is that they're sometimes unemployed people or students hoping to create a popular open source project, and use it to find a job.

They aren't going to care about any of the advice in the article about not posting slop -- finding a job is (of course?) more important to them.

Can't really say they are doing anything wrong, maybe I too would have? ... Just that large scale, doesn't work

The number is 9

9% not accurate answers, for Gemini 3. (I think that's a lot!)

Have you seen Talkyard Blog Comments? It's open-source and based out of Europe. https://blog-comments.talkyard.io. (I'm developing it.)

legacy WP blog ... users should be able to ...

(What's your blog about?)

suddenly have 215 new files to check in!

How big is your repo, if I may ask?

Personally I store vendored dependencies in a submodule, where I can squash history, if it grows too large.

Good points. But what do you mean with 3: "lockfile poisoning attacks, by making them more complicated" — making the lockfiles more complicated?

Also, 4) Simpler to `git diff` the changes, when you have the source locally already :- )

Scala could be one example? When I upgraded to a newer version of the standard library (the Scala 2.13 or Scala 3 collections library), there was a tool, Scalafix [1], that could update my source code to work with the new library. Don't think it was perfect (don't remember), but helpful.

[1] https://scalacenter.github.io/scalafix/

Then you might find Talkyard interesting: https://blog-comments.talkyard.io — reminds of Disqus, in that it's threaded, best first (optionally). (I'm developing it.)

showing some CORS error

In my case, I found it annoying when cookies gradually stopped working, and eventually I had to make the software use custom HTTP headers instead of cookies.

Seems that mostly spammers comment

The more interesting the contents of the blog is, the more real humans will like it and post comments? (if they can find it)

But a "Our company posts something each day, even if nothing has happened" blog, or AI fluff, attracts only spammers?

Could one say that humans are trained very differently from AIs?

If we (humans) make confident guesses, but are wrong — then, others will look at us disappointedly, thinking "oh s/he doesn't know what s/he is talking about, I'm going to trust them a bit less hereafter". And we'll tend to feel shame and want to withdraw.

That's a pretty strong punishment, for being confidently wrong? Not that odd, then, that humans say "I'm not sure" more often than AIs?

Yes, many _humans_ here hallucinate, sort of.

They apparently didn't read the article, or didn't understand i, or disregard from it. (Why, why, why?)

And they fail to realize that they don't know what they are talking about, nevertheless keep talking. Similar to an over confident AI.

On a discussion about hallucinating AIs, the humans start hallucinating.