sigmoid.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A social space for people researching, working with, or just interested in AI!

Server stats:

599
active users

#context

1 post1 participant0 posts today

Efforts to reduce animal experiments are important and should be pursued. But despite progress in , , and models, I’m not convinced we’re there yet — especially in , where and systemic matter. However, I do think we should stay committed and aim for reduction by all available means. I recently came across this article, which gives a good overview of the current state of the field:

🌍 genengnews.com/topics/translat

GEN - Genetic Engineering and Biotechnology News · Why We Still Need Animal Research in a World of AI and OrganoidsBy Jason Shepherd, PhD

#ContextEngineering - Unlocking #AgenticAI’s True Potential

> Today's #LLMs are far more complex with context size of millions of tokens and the ability for calling external systems, tools, and even #agentic orchestration with multi-agent #AI systems. #Context has therefore evolved beyond the prompt to include System Prompt, User Input/Prompt, Memory, Retrieved Information (#RAG etc.), information on tools (#MCP), responses from tools, and structured output format

deepgains.substack.com/p/conte

Deep Gains · Context Engineering - Unlocking Agentic AI’s True PotentialBy Arun S

#HiddenHashtags continuing to inject #TimelineIntruders.

Readers get displayed different Posts depending on their method of reading.

I can't tell why some Posts are on my Timeline with #HiddenHashtags.

My Timeline - but not easily under my control?

Hashtags can create #Context.
Hashtags can attract specific types of users.
A visible hashtag experience can be very different to a hidden hashtag experience.

Hiden or visible hashtag #TrumpIsLordJesus.
Different UX.
Client dependent.

Continued thread

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. 🤯

I'm trying to correct a longtime gap by finally reading Twain's Tom Sawyer and Huckleberry Finn books, and have to admit—I hate them. Yeah, there's real craft here, and some great storytelling, but OMG it's nonstop n****r n****r n****r and I'm sure Twain was trying to be on the right side of things but it's just relentless. Reminds me how we queer folk are supposed to revere The Boys In The Band, which has a similar problem, but with sad gayness.

Replied in thread

@mcc some options you may or may not be aware of:

  • switch to librewolf (recommend!)
  • set extensions.pocket.enabled to false in about:config
  • set toolkit.legacyUserProfileCustomizations.stylesheets to true in about:config and put #context-savelinktopocket { display: none } in <firefox-profile>/chrome/userChrome.css

this last one lets you hide a bunch of junk in right click menus. my current settings:

#context-navigation,
#context-sep-navigation,
#context-sendimage,
#context-print-selection,
#context-bookmarklink,
#context-stripOnShareLink,
#context-take-screenshot,
#context-sep-screenshots,
#context-searchselect,
#context-searchselect-private,
#context-translate-selection,
#context-ask-chat,
#frame-sep,
#context-savelinktopocket,
#context-sendlinktodevice,
#context-sep-sendlinktodevice,
#context-viewpartialsource-selection,
#context-inspect-a11y,
#sidebarRevampSeparator
{
display: none;
}

Update on // foss.events:

registration has opened and description updated for

ConTeXt meeting by context group, Ryszard Kubiak on 22-29 August 2025 in Holiday site KREFTA in #Chmielno, #Poland

Find out more on foss.events/2025/08-22-context

Official account: @context
Official hashtag(s): #ConTeXt

// foss.eventsConTeXt meeting on // foss.eventsEverything in a nutshell about ConTeXt meeting on // foss.events