@hamishcampbell (8/9)
Since you have already expressed your #mind on the issues of #stupid-individualism I think it would be interesting to #explore specific-case #benefits of it, based on cases which had #positive #outcome . In the same fashion, it could be interesting to explore the #negatives of a #shared-governance and #open-processes in #context of #projects which had #negative outcome from it, as a #thought-exercise .
...
@hamishcampbell (6/9)
But it doesn't look to me like the #world works that way.
-
I am also #curious , since you have an interesting #concept of #compost there, whether it would #scale . On the same #note , if you were to gain #mass #attention with your #website , would it #benefit it by bringing right #people , or would it #rot it? You mention #preventive systems for avoiding that kind of rot. I would like to hear more about that.
...
@hamishcampbell (7/9)
You speak broadly about a lot of things, here I am thinking more from the #context of #tech #projects . In terms of #key-figures and #stupid-individualism I would try to not go into extremes. While I agree that the #issue #exists big time, I could come up with #examples where both could be either #good or #bad , depending on the #scenario .
...
@warmsignull take you up on that, what do you think the story of alt tech/media/culture here https://hamishcampbell.com/ and then the concrete native projects that row from this #OMN
@hamishcampbell
So this might not be the best medium for that kind of conversation.
(1/9)
Also a fan of alternative lifestyles here.
That is a great #tip and a #question .
I am intrigued. Hard to argue with most of what I have read so far.
So first of all, this is quite a lot of #context and #information . It would also be very hard to not make any #assumptions without having been exposed to it all for an extended period of #time .
-
As a #good-intentioned and #explorative question:
...
Donating the Model Context Protocol and Establishing the Agentic AI Foundation
#HackerNews #Donating #the #Model #Context #Protocol #Agentic #AIFoundation #AIResearch #TechForGood
Launch HN: Nia (YC S25) – Give better context to coding agents
#HackerNews #LaunchHN #Nia #YCS25 #coding #agents #context #technology
#Development #Analyses
Why is CSS so tough for AI? · The reason Tailwind CSS is more AI-friendly https://ilo.im/168axz
_____
#Programming #Coding #VibeCoding #AI #Context #WebDev #Frontend #HTML #CSS #TailwindCSS
Let the little guys in: A context sharing runtime for the personalised web
#HackerNews #Let #the #little #guys #in #A #context #sharing #runtime #for #the #personalised #web #contextsharing #personalisedweb #HackerNews #techinnovation #webdevelopment
⁂ Article
Moving topics/contexts between communities
Moving contexts (aka topics/threads) between audiences (aka categories/communities) should be something that can be communicated outward.
NodeBB is experimenting with using the Move activity to communicate this to other instances.
When a context is moved from one audience to another, the object and all of its descendants go with it.
Solved! 🥳
This was a pretty "interesting" bug. Remember when I invented a way to implement #async / #await in #C, for jobs running on a threadpool. Back then I said it only works when completion of the task resumes execution on the same pool thread.
Trying to improve overall performance, I found the complex logic to identify the thread job to put on a pool thread a real deal-breaker. Just having one single MPMC queue with a single semaphore for all pool threads to wait on is a lot more efficient. But then, a job continued after an awaited task will resume on a "random" thread.
It theoretically works by making sure to restore the CORRECT context (the original one of the pool thread) every time after executing a job, whether partially (up to the next await) or completely.
Only it didn't, at least here on #FreeBSD, and I finally understood the reason for this was that I was using #TLS (thread-local storage) to find the context to restore.
Well, most architectures store a pointer to the current thread metadata in a register. #POSIX user #context #switching saves and restores registers. I found a source claiming that the #Linux ( #glibc) implementation explicitly does NOT include the register holding a thread pointer. Obviously, #FreeBSD's implementation DOES include it. POSIX doesn't have to say anything about that.
In short, avoiding TLS accesses when running with a custom context solved the crash. 🤯