What's cooking on Sourcehut? Q2 2026
SourceHut has been focused on various internal improvements and addressing challenges in the past quarter. The team is working on a grant proposal for EU funding and enhancing their GraphQL APIs. Additionally, they are tackling issues related to DDoS attacks and spam sign-ups while implementing new features for user access.
- ▪Drew has been preparing a grant proposal for funding from the EU alongside other open source partners.
- ▪The team is currently addressing DDoS attacks and has implemented measures to mitigate their impact.
- ▪New features, such as SSH deploy keys for repositories, have been introduced to improve user access.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Sourcehut |
| Canonical URL | https://sourcehut.org/blog/2026-05-28-whats-cooking-q2-2026/ |
| Publication time | Fri, 29 May 2026 14:40:21 +0000 |
| Retrieval time | 2026-05-29T14:50:01.336Z |
| Last seen | 2026-05-29T14:50:04.438Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | gjz0L7tcpfBx |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Hello everyone! It’s time for another quarterly update, keeping you up to date on what we’re cooking up here at SourceHut. Drew’s update This past quarter I found myself mostly focused on “invisible” labor for SourceHut, which will make for a boring update from me this time. Most of my time was spent preparing a grant proposal, jointly with some other open source forges and related partners, to apply for funding from the EU. We’ll learn how that went sometime next quarter! Otherwise I’ve been focused on greasing the wheels and keeping the lights on – doing code reviews, fixing little bugs here and there, handling user support, mitigating rolling DDoS attacks (Conrad will elaborate on these in a moment), dealing with the finances (it’s tax season), and enjoying some rest after dealing with…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Sourcehut.
Discussion
0 commentsMore from Sourcehut
