Search
25 results for “dachary”
-
@dachary Woot! Glad you approve! Thanks for your support of #ProjectTapestry 🫶
-
I should also add that we've lived here for 18 years, so an event every 2-3 years isn't *too* horrible.
I'm not sure what we'd do, frankly, which is why we haven't bothered with cameras.
When #LilyTheCat returns, I'd like to put up a sort of "doorbell" bluetooth LE thing that looks for her tracker and lets us know when she's home. Perhaps one on either end of the yard just so we know when to open the door for her.
-
@dachary @forgefriends I mean if you invent a name and a logo and attribute it to the public domain, no one else can register it as a trademark, right? You just need to timestamp the time of invention (#OpenTimestamps and Twitter or something) and any party being sued by someone falsely claiming the copyright/trademark should be able to defend themselves using that.
-
@humanetech @dachary I think nobody will move off of #github as long as there is no #federation support in any of the #selfhostable alternatives!
As soon as there is, I think people will start moving away. Not many, but some. Federation is a must-have, because otherwise creating accounts just for reporting a bug is just too much of a task for the average user and sometimes even for more "advanced" users. I certainly would be much happier if I could just use my own instance and create a bugreport/issue/etc on some project hosted somewhere else!
Of course, #sourcehut does already provide everything we would need. Also, Email is THE workflow with #git IMO. But I acknowledge that its just not enough for most users and they want some kind of #forge and bling-bling website like github. I do not blame them. -
@paul @gitea @Bobo_PK @dachary @forgefriends @sebastian @stevenroose W.r.t the criminal enterprises claim— criminals use #cryptocurrency & also banks. We don’t cancel banks just b/c criminals use them. We don’t cancel cars just b/c drive-by shootings happen. More generally, we don’t oppress legitimate users of a tool just because there are some bad actors. #Unbanked people should not be excluded from commerce on the basis that thieves exist.
-
@estherpayne You're very welcome Esther.
Right now many of us involved in the "Forge Friends" #Gitea (ActivityPub) Federation community are running on very little sleep today, following yesterday's unfolding events.
I know that Dachary has reached out to Bradley there at SFC and as a (stunned) community we're currently weighing options and possible scenarios moving forward.
But yes, I wanted to reach out about the multicast project status and see what meaningful efforts might be contributed, so I'll probably follow up with you later in that regard since you're the outreach PoC.
And thank you for the presentation again, and especially for helping to keep #RFC1984 front row and center in our conversations about #FOSS and the individual's #Privacy, in the face of so much oppositional pressure.
Kindest regards,
#tallship
⛵
. -
kittens.eff.org/deeplinks/2020…
This looks like a great conversation with @pluralistic and others on the topic.
They mention that #AdversialInteroperability is now #CompetitiveCompatibility .
/via cybre.space/@jauntywunderkind4… @jauntywunderkind420
@dachary -
"Skills are different formats for docs, one that pre-packages them into self-contained cartridges that you can share and reuse in LLM contexts. Knowing this, documentarians must acknowledge that skills are needed and useful, and work to operationalize their generation, distribution, and maintenance based on the documentation.
Start with meta skills as a way to ensure that new skills are made in accordance with existing docs, for example by calling a docs MCP server, and following their style. A skill that creates new skills following your editorial advice and rules is a quality checkpoint that also provides better skills performance (because LLMs benefit from great docs as much as humans).
Next, create agentic workflows that check if skills drift from existing documentation (again using an MCP server) and open pull requests to fix them if they do. Use evals and skill validators in CI pipelines (I use Dachary’s) to ensure skills aren’t broken or hallucinating. These are all safety nets in case meta skills aren’t used or skills aren’t updated.
Lastly, involve tech writers as consulted parties to make sure that skills knowledge is reflected in docs and identify chances for skills creation and improvements. You can also promote skills in user-facing docs as an interactive, LLM-friendly complement to docs themselves. Working on ways to “skillify” existing documentation is another good path."
https://passo.uno/skills-are-docs/
#TechnicalWriting #Claude #Skills #AI #LLMs #GenerativeAI #ClaudeSkills #Markdown
-
While #GitHub #Copilot doesn't violate free #software licences (see ⬆️), there are plenty of reasons to #GiveUpGithub anyway. Here are a few:
1. Since we're #FOSS developers, our tools should be #FreeSoftware too.
2. Monopolies are never a good idea.
3. By using a walled garden, we're excluding potential contributors.
4. By using #Microsoft products, we're supporting a producer of #tracking malware and an #NSA collaborator.Instead, we should switch to #Git platforms running @gitea, such as @codeberg. Also, @dachary and others are already working hard on #forge federation in the @forgefriends project.
Read more on the #ForGoodEyesOnly blog: https://forgoodeyesonly.codeberg.page/blog/2022/07/why-github-copilot-doesnt-violate-free-licences/#why-we-should-still-giveupgithub
-
While #GitHub #Copilot doesn't violate free #software licences (see ⬆️), there are plenty of reasons to #GiveUpGithub anyway. Here are a few:
1. Since we're #FOSS developers, our tools should be #FreeSoftware too.
2. Monopolies are never a good idea.
3. By using a walled garden, we're excluding potential contributors.
4. By using #Microsoft products, we're supporting a producer of #tracking malware and an #NSA collaborator.Instead, we should switch to #Git platforms running @gitea, such as @[email protected]. Also, @[email protected] and others are already working hard on #forge federation in the @forgefriends project.
Read more on the #ForGoodEyesOnly blog: https://forgoodeyesonly.codeberg.page/blog/2022/07/why-github-copilot-doesnt-violate-free-licences/#why-we-should-still-giveupgithub
-
While #GitHub #Copilot doesn't violate free #software licences (see ⬆️), there are plenty of reasons to #GiveUpGithub anyway. Here are a few:
1. Since we're #FOSS developers, our tools should be #FreeSoftware too.
2. Monopolies are never a good idea.
3. By using a walled garden, we're excluding potential contributors.
4. By using #Microsoft products, we're supporting a producer of #tracking malware and an #NSA collaborator.Instead, we should switch to #Git platforms running @gitea, such as @codeberg. Also, @dachary and others are already working hard on #forge federation in the @forgefriends project.
Read more on the #ForGoodEyesOnly blog: https://forgoodeyesonly.codeberg.page/blog/2022/07/why-github-copilot-doesnt-violate-free-licences/#why-we-should-still-giveupgithub
-
While #GitHub #Copilot doesn't violate free #software licences (see ⬆️), there are plenty of reasons to #GiveUpGithub anyway. Here are a few:
1. Since we're #FOSS developers, our tools should be #FreeSoftware too.
2. Monopolies are never a good idea.
3. By using a walled garden, we're excluding potential contributors.
4. By using #Microsoft products, we're supporting a producer of #tracking malware and an #NSA collaborator.Instead, we should switch to #Git platforms running @gitea, such as @codeberg. Also, @dachary and others are already working hard on #forge federation in the @forgefriends project.
Read more on the #ForGoodEyesOnly blog: https://forgoodeyesonly.codeberg.page/blog/2022/07/why-github-copilot-doesnt-violate-free-licences/#why-we-should-still-giveupgithub
-
While #GitHub #Copilot doesn't violate free #software licences (see ⬆️), there are plenty of reasons to #GiveUpGithub anyway. Here are a few:
1. Since we're #FOSS developers, our tools should be #FreeSoftware too.
2. Monopolies are never a good idea.
3. By using a walled garden, we're excluding potential contributors.
4. By using #Microsoft products, we're supporting a producer of #tracking malware and an #NSA collaborator.Instead, we should switch to #Git platforms running @gitea, such as @[email protected]. Also, @[email protected] and others are already working hard on #forge federation in the @forgefriends project.
Read more on the #ForGoodEyesOnly blog: https://forgoodeyesonly.codeberg.page/blog/2022/07/why-github-copilot-doesnt-violate-free-licences/#why-we-should-still-giveupgithub
-
"Can I convince AI to write useful content with minimal input from me? No. The input required is substantial; it's just a different kind of input than writing from scratch. Instead of staring at a blank page, I'm interrogating drafts, verifying claims, reframing angles, and restructuring articles. It's editing rather than writing, but it's not less work.
Can it provide a novel editorial take? Sometimes. The models produce serviceable takes that, with significant editorial shaping, become useful articles. But the novel connections, the thematic throughlines, the "this matters because of what we published last week" insights all come from me.
Can it produce accurate articles? Not without heavy verification. Every single article required factual corrections. Some were minor (wrong pipeline phase names, singular vs. plural). Some were serious (fabricated implementation details, wrong OWASP rankings, misleading CVE framing). The pipeline's verification step catches a small number of them. The rest require an editor who reads critically and clicks every link.
Can I edit out the AI writing tics? Mostly. The automated copy-editing pass handles the obvious markers. The subtler ones take manual work, and I'm still learning which tics I'm missing in my own editing passes.
I still think, for my needs, the pipeline is a useful tool for editorial content production. It's just not the "AI writes the blog" story that the stats at the top of this article might suggest. It's more like "AI produces a structured first draft that an experienced editor spends 90 minutes turning into something publishable." Whether that's worth it depends on what you value."
https://dacharycarey.com/2026/03/26/drafting-editorial-content-with-ai/
#AI #GenerativeAI #LLMs #TechnicalWriting #Writing #Blogging #Blogs
-
"I ask AI to explain things all the time. If I observe it do something that I want to learn more about, I ask it. I look at its outputs and ask it to explain decisions it made or how it implemented something. I ask it to help me brainstorm about things, help me think through edge cases or performance considerations, you name it. If the thing that it is explaining has some implication I need to verify, I ask it to find me a link that backs up what it is saying. And then I look at the link to make sure the content is real, comes from a reasonable source, and actually backs up what the AI says. And probaly also ask it questions about the surface area around the thing, until I’m sure I understand it.
If you approach the AI upskill process as a collaborative learning process, where you can interrogate the tool you’re learning about its capabilities, how and why it’s chosing to do the things it’s doing, and to explain anything you don’t understand along the way - you’re unlocking a super power.
AND you have the comfort of knowing you’re asking all your questions of a talking box that won’t remember what you asked the next time it chats with you. So even if you do think it’s judging you, it has amnesia and that judgement won’t last beyond closing the session!"
https://dacharycarey.com/2026/02/23/upskilling-in-ai-age/
#TechnicalWriting #AI #LLMs #AIAgents #Chatbots #SoftwareDocumentation
-
"Over the weekend, I spent about 10 hours working with Claude to manually validate 578 coding patterns across a range of languages and coding tasks for my Agent Skill Report. We had to deep dive into standard library docs, package-specific documentation, large enterprise docs, and personal blogs. My goal was to ensure that every API and configuration pattern I was using in a behavioral evaluation experiment reflected the current guidance from official sources. My learnings about agent docs access patterns were secondary to this project, but the results are a rich treasure trove of data that may inform how I use agents with docs in the future. As a technical writer who has worked on SaaS and developer docs for the last decade, honestly, my findings made me a little sad.
(...)
My high-level takeaway was this: I expected an agent to try to use docs like I do, and was very surprised when it didn’t.
(...)
Over the course of validating 578 patterns across 20 different skills, my agent and I built up a pretty comprehensive picture of what documentation access patterns actually work for agents, and which ones don’t. I had my agent keep a running reference doc of its learnings, and by the end of the project, the patterns were clear enough to categorize."https://dacharycarey.com/2026/02/18/agent-friendly-docs/
#TechnicalWriting #TechnicalCommunication #AI #AIAgents #LLMs #Chatbots #AgenticAI #SoftwareDocumentation #APIs #Docs #Documentation
-
Ooo forgot to post this, but we had a #cheesestodon -themed special treat over the weekend. Inspired by @natania . It’s been too long since we did this - thanks for the inspiration! It was delicious.
-
Ooo forgot to post this, but we had a #cheesestodon -themed special treat over the weekend. Inspired by @natania . It’s been too long since we did this - thanks for the inspiration! It was delicious.
-
Ooo forgot to post this, but we had a #cheesestodon -themed special treat over the weekend. Inspired by @natania . It’s been too long since we did this - thanks for the inspiration! It was delicious.
-
Ooo forgot to post this, but we had a #cheesestodon -themed special treat over the weekend. Inspired by @natania . It’s been too long since we did this - thanks for the inspiration! It was delicious.
-
Khi da bị cháy nắng, cảm giác gel-cream làm dịu nhanh đáp ứng như thế nào so với kỳ vọng ban đầu.
https://marketplace.tripmap.vn/product/gel-cream-swissoxx-ultra-detox-lifting-sieu-phuc-hoi-lam
#dachaynang #gelduongda #camgiaclamdiu #danhgiasanpham #chamsocda
-
#DeCharybdeEnScylla #meilleursvoeux
Boris #ELDIABLO souhaite ce qu'il faut à qui il faut.
(Illustration réalisée pour l'Itinéraire de Janvier 2022)
L'Itinéraire est une publication périodique , contribuant à la réinsertion sociale ; ayez une pensée spéciale pour les galériens de ce monde, y'en a qui rament toute l'année.
-
📢New Working Paper out now!
#SFB1265 PI Séverine Marguin and Caroline Datchary (Université Toulouse Jean Jaurès) investigate the socio-spatial development of #startups in Berlin and juxtapose the concepts of #space and #ecology.
Read it here: https://sfb1265.de/en/publications/publication/datchary-c-marguin-s-2023-ecology-and-space-a-socio-spatial-investigation-on-the-development-of-startups-working-paper-no-10/
#sociology #startupscene #Berlin #spatialresearch -
Mit Agri-Photovoltaik werden Agrarflächen doppelt genutzt: für Landwirtschaft 🌱 und Energiegewinnung 🌞
Prof. Dr. Tim Krieger von der Universität Freiburg und Dr. Max Trommsdorff von Fraunhofer ISE erzählen im Interview, welche Chancen damit einhergehen und in welchem Bereich die Freiburger Agri-PV-Forschung als international führend gilt 🔬
🌞Zum Interview: https://ufr.link/agri
Fun Fact: Wussten Sie schon, wie vielseitig Agri-PV genutzt werden kann?
🐑 Auf Grünland können Module so angeordnet werden, dass Schafe oder Rinder darunter grasen.
🍅Über Obstplantagen oder Weinbergen können dachartige Konstruktionen stehen, durch die man mit Traktoren hindurchfahren kann.
🌊 Es gibt sogar „Aquavoltaik“: In Garnelenfarmen in Vietnam etwa überspannen die Module Wasserbecken, liefern Strom für Pumpen und kühlen zugleich das Wasser.#UniversitätFreiburg #UniFreiburg #Nachhaltigkeit #Energiewende #AgriPV
