Show HN: Silo – S3-compatible object storage, a maintained fork of MinIO

Pigsty and SILO contributors· Aug 6, 2026 · 4:05 PM UTC ·1 min read · 0 reactions · 0 comments · 9 views

S3-compatible object storage maintained by Pigsty, with security updates, versioned releases, a restored console, and operational continuity.

About this source

Hacker News (Front Page) files mainly under programming. We currently carry 1,234 of its stories. Top-voted stories on Hacker News.

All Hacker News (Front Page) coverage →

Original article

SILO · Pigsty and SILO contributors

Read full at SILO →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

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	SILO
Canonical URL	https://silo.pgsty.com
Publication time	Thu, 06 Aug 2026 16:05:11 +0000
Retrieval time	2026-08-06T18:05:47.594Z
Last seen	2026-08-06T18:05:47.594Z
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	None yet
Summary source text	contentText
Citation coverage	No WeSearch summary has been generated for this story yet.
Cluster	O-b_qwS3vAee · 1 stories
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)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

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.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

✓MAINTAINED SURFACEWhat stays maintainedBuilds and dependencies for the active release lineApplicable security fixes and advisoriesFocused fixes for reproducible defectsVersioned artifacts and documentationA release typically every 1–2 months, at most a quarter

Excerpt limited to ~120 words for fair-use compliance. The full article is at SILO.

Anonymous · no account needed

Discussion

0 comments