First, we sincerely apologize for the recent downtime and the disruption it caused. We understand that many buyers and community members were left without clear information during the transition, and that this created frustration and concern.

Tindie is now owned by EETree LLC, a Washington State company. Our team took over Tindie because we believe it remains an important platform for makers, hardware creators, engineers, and independent sellers around the world. The recent transition was more complex than expected. Tindie runs on an older technical framework with many connected services, and the migration from the previous operating environment to the new one took longer and caused more disruption than anyone wanted.

We know this was not the experience the Tindie community deserved.

Our immediate focus is to stabilize the platform, resolve payment and order-related issues, and support sellers and buyers through the transition. If you have an order-related concern, please contact Tindie support so the team can review your case directly.

WHAT WE ARE FOCUSED ON

Stabilizing the platform

Restoring reliable access for buyers, sellers, and the community.

Resolving open issues

Working through payment, refund, and order concerns case by case.

Investing for the long term

Renewing attention, support, and improvements for the community.

We also want to be clear about our long-term intention: we did not take over Tindie to let it fade away. We took it over because we believe it deserves renewed attention, investment, and support.

Tindie has always been more than just a marketplace. It is a place where independent creators, makers, and hardware enthusiasts can share useful products, tools, kits, modules, and ideas with the world. We want to preserve that spirit while improving the platform step by step.

Over the coming weeks and months, we will share more about our plans and will listen carefully to feedback from sellers, buyers, and the broader community.

Thank you for your patience and continued support. We know trust must be earned through action, and we are committed to doing that.

Sincerely,

Gongyu Su

On behalf of the Tindie Team

Comments URL: https://news.ycombinator.com/item?id=47945522

Points: 51

# Comments: 31

🏷️ My labels
- ❌
❌
29 April 2026 at 08:16

H N
Low-Compilation-Cost Register Allocation in LLVM-Based Binary Translation
29 April 2026 at 06:47

Low-Compilation-Cost Register Allocation in LLVM-Based Binary Translation

H N

29 April 2026 at 06:47

By: matt_d

Article URL: https://dl.acm.org/doi/abs/10.1145/3767295.3803591

Comments URL: https://news.ycombinator.com/item?id=47944931

Points: 33

# Comments: 0

🏷️ My labels
- ❌
❌
29 April 2026 at 06:47

H N
HardenedBSD Is Now Officially on Radicle
29 April 2026 at 06:38

HardenedBSD Is Now Officially on Radicle

H N

29 April 2026 at 06:38

By: lftherios

Article URL: https://hardenedbsd.org/article/shawn-webb/2026-04-26/hardenedbsd-officially-radicle

Comments URL: https://news.ycombinator.com/item?id=47944864

Points: 84

# Comments: 13

🏷️ My labels
- ❌
❌
29 April 2026 at 06:38

H N
Bugs Rust won't catch
29 April 2026 at 02:19

Bugs Rust won't catch

H N

29 April 2026 at 02:19

By: lwhsiao

Article URL: https://corrode.dev/blog/bugs-rust-wont-catch/

Comments URL: https://news.ycombinator.com/item?id=47943499

Points: 349

# Comments: 168

🏷️ My labels
- ❌
❌
29 April 2026 at 02:19

H N
When the Internet Was a Place
29 April 2026 at 01:36

When the Internet Was a Place

H N

29 April 2026 at 01:36

By: herbertl

Article URL: https://www.frontporchrepublic.com/2025/09/when-the-internet-was-a-place/

Comments URL: https://news.ycombinator.com/item?id=47943190

Points: 67

# Comments: 23

🏷️ My labels
- ❌
❌
29 April 2026 at 01:36

H N
Regression: malware reminder on every read still causes subagent refusals
28 April 2026 at 23:59

Regression: malware reminder on every read still causes subagent refusals

H N

28 April 2026 at 23:59

By: thomashobohm

Not sure if anybody else has experienced this, but for my job I've been playing around with Claude Managed Agents to run code generation tasks in our repo. Every read operation in the managed agent is appended with a system prompt instructing Claude to scan the file for malware; Claude then wastes a bunch of time and tokens (money) performing the analysis; then, once the agent has confirmed that it is not malware, it still interprets the appended prompt to mean that it is disallowed to augment or write any code, and quits. And we're charged for every session that this happens in. Posting here because apparently they only addressed the issue in the past because of a Hacker News discussion. So here's hoping they'll see this and prioritize fixing it again so we can stop losing money.

Comments URL: https://news.ycombinator.com/item?id=47942492

Points: 229

# Comments: 122