17 karma · joined July 17, 2019
Supports public (permanent CDN), expiring (TTL-based), and private (auth-gated) uploads. --json flag for scripting/agents.
Built on Cloudflare Workers + R2. Currently waitlist, happy to give HN folks early access.
I was pleasantly surprised with how both Codex and Claude helped me with this. I’ve been meaning to learn ios dev for the longest time and I’m really glad I finally managed to give it a try while having enough help doing it! I’m a React developer for the most part.
It shows live departures and mobile ticket integration with Apple Wallet passes, track predictions, with plans for alerts, GPS-based train map, Live Activities… and more.
I’d love help from the community testing it, finding bugs, and suggesting improvements. It’s been a fun side project, and I’m looking for feedback on what features matter most to daily commuters.
TestFlight: https://testflight.apple.com/join/da4zcqfm Feedback & roadmap: https://feedback.vianj.app
This React TypeScript project demonstrates a Braintree OAuth integration flow between two merchants. It showcases how Merchant A can obtain authorization from Merchant B to perform actions on their behalf using Braintree's OAuth and transaction APIs.
In this example, Merchant A provides this application to Merchant B, allowing them to:
Grant OAuth permissions to Merchant A
Allow access to customer payment methods
Enable facilitated transactions
The integration uses two main Braintree APIs:
Access Token API - For OAuth authentication
Transaction API - For creating Shared Vault Transactions
FEATURES
OAuth connection flow
Token management and storage
Shared vault transaction processing
Real-time transaction status updates
Error handling and user feedback
Hope this is helpful to someone!
If you were to add a preview functionality of each component, this would already look A LOT like the Bit platform.
Personally, I've been trying to figure out a way to create a component library where my components are easily shareable and importable, but haven't yet come to a real solution. Bit is a good one but I am not yet ready to pay per component after my 20 free components are used up.
I think this would be actually extremely useful to me personally if you added these two things:
- component live preview (perhaps with mock props/data?)
- a way to store the components in the cloud so that they can be important into any project, where the source of truth is in this cloud platform
In the future, you could add things like:
- component-level testing
- AI features
- version control and PR reviews
- CI integrations / other integrations
But good point, I totally forgot about BBEdit
Either way, seems cool, would love to try it out as an open source project.
But does this basically mean that you now provide the entirety of the code to users? This includes HTML and JS, since it now lives entirely on the host site, easily accessible to the developers of the host site. Is this something that was discussed and was eventually agreed upon? I would be curious to learn why it was ultimately decided that you are OK with users having the raw HTML and JS code that powers your product.
Furthermore, it also makes it more difficult for users to receive UI updates. If there is an important bug fix or enhancement, users would need to upgrade to the latest HTML/JS "package" that controls the web component, correct?
Of course with an iframe, any updates are seen immediately on the user side.
Curious to hear your thoughts!
I wonder if a legit subscription service, for perhaps a select group of items that a user consistently purchases, would work. Could be complicated when things like eggs fluctuate so much in price.