https://traice.market

I personally want an OSS Union for situations in which trillion dollar megacorps attempt to bully OSS interop project maintainers and give them trauma over C&Ds which they get almost no support for.

I would pay at least $20 per month to be part of this union. I would like it to protect all OSS devs even if they have no propensity to pay.

I think this will be an important tool to fight enshittification.

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

Points: 1

# Comments: 2

I kinda got sick of having to give secrets to my agents and all the potential leakage in the pipeline (with the harness, the model router, the model provider, the training set, the chat application etc etc) so I decided to make peardrop.fyi - this tool allows your agent to declaratively generate secret request pages/links which you can fill in via web or CLI. The agent can determine a script that runs once the values are received or can put them in a target folder. This is useful if you want to put something in your machine vault/keychain without either giving access to the credentials or the browser to the agent.

here is the repo: https://github.com/smashah/peardrop

(cli, core and self-hostable relay are all open source)

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

Points: 2

# Comments: 0

npx txtadev inbox

and

npx txtadev read

Introducing https://txta.dev - as long as you have an existing Github account and a public key you can send/receive messages securely which only the recipient can read!

It's like facebook poking for devs!

Send me a message with this command :)

npx txtadev smashah "hello world"

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

Points: 3

# Comments: 1

I made peardrop.fyi because I have now perfected the agent-driven software factory stack. Now I only interface with an agent called Pennyworth that uses an aviation/Gotham/billions based cast/operative org structure to get stuff done. This means that sometimes Pennyworth determines that 5 projects are blocked due to lacking credentials/secrets/keys/JSONs etc.

Sometimes I talk to it via discord, whatsapp etc and therefore I would prefer that none of these secrets make it anywhere in the chat. I also don't want it to be going through the model routers, OTel, model providers, etc etc.

so this is why I made peardrop.

Peardrop uses pears SDK/HyperDHT a cli and an optional (default) relay (self hostable) to enable a pleasant and secure experience for transferring secrets/files to your agent's target location no matter where it is, no matter where you are.

The agent is instructed to create a declarative UI for the credentials request using toml and markdown. This allows you to have all the context/links/instructions you need in the peardrop link itself to actually find the right credentials and deliver it into the peardrop.

This ease of use for the submitter also makes it a good tool for requesting creds/secrets from your nontechnical clients.

The service is self-hostable, open-source and mainly free but due to the limitations of the web environment (no udp support), there is a hosted relay, and because I want to use every project as a learning experience, I have implemented x402 payments for using the relay for anything over 5mb - practically this means that nobody that uses it for it's actual use case (sending creds/secrets) will ever actually need to pay for the relay.

Here is the gh: https://github.com/smashah/peardrop

p.s if anybody has any work they need done, want to learn more about my agentic coding system, or want to get their vibecoded project over the line then please DM me. thank you.

(edit, oh wait there is no way to DM people on here, just make an issue in the gh or something while i figure out a way to send me a dm)

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

Points: 3

# Comments: 1

Services like pirate[dot]kred use that information to link your books to your payment pages (substack is supported).

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

Points: 1

# Comments: 0

Every AI lab subsidizes access to their models partly to get their hands on your sessions. In this AI goldrush, models are the shovels and our traces are the wood the shovel-makers build them from. So if our working sessions are that valuable, why are we giving them away for a mere discount to only one model provider at a time? I wanted to answer the question: what if we could sell our own traces to model providers directly in a way where the data is never at risk? That's why I'm building traice.market (WIP) and Traicer. Traicer is the open source collection service that runs on your machine, and you route selected Claude Code / Codex / OpenCode calls through and it saves to your own S3 compatible bucket (thanks alchemy.run and varlock for making integrating this feature securely very simple!)

Each supported call gets credential-stripped, redacted (keys, JWTs, DB URLs, emails), encrypted with AES-256-GCM, and written to an S3 bucket you own. Keys never leave your machine. When traice.market is ready, it will let you sell traces without us ever being able to touch or read them: the marketplace only sees signed content-free metadata (provider, model, token counts, hashes), and a sale requires your explicit approval, with delivery re-encrypted on your machine to the buyer's key.

I would love any feedback/questions etc.

thanks!

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

Points: 3

# Comments: 1