sambroner
Joined 8 years ago
Karma
1,050
Submissions
201
Member since
Aug 23
sambroner.com
github.com/SamBroner
twitter.com/SamBroner
View on Hacker NewsRecent submissions
Comment · 9 months ago
sambroner.com
Comment · 1 year ago
How would this be tooled? A chargeback, a deep link to the cancel page, an API connection between bank and subscription?
Chargeback is easy because it's under the card co's control. Deep link would require knowing the cancel page of every sub, plus handling auth factors. API connection would two way integration, with scoped auth between every bank and every service. Hopefully managed by an SI or aggregator, but the business model sounds hard (the bank doesn't mind the chargeback, the SaaS doesn't want the cancelation, so who pays?)
Comment · 1 year ago
When I was working on the Fluid Framework, now basically Microsoft's Copilot Pages, we built a URI Schema to let in-app widgets specify the code that would let users interact with the underlying data.
Example: you open the app and load a specific document. Simplified, but this loads a "boot loader" and connects to the data feed of the document. The boot loader reads the first few operations which contains the widget/app code to load all the UX of the application. Examples of widgets would be a whiteboard, a text editor, a table widget, an identity card, a latex widget, etc.
Widgets could be posted outside of the document because any loader that could read the URI could parse it and understand the app code to load and data feed to connect to.
I'm still somewhat infatuated with the design and I'd like to see it much more widely adopted. Security issues were, of course, a major issue.
Comment · 1 year ago
I love this project! The UI feels so delightful and well thought out. I guess I found another weekend (multi-week?) activity.
If you're looking for hackathon projects, the E-ink ecosystem is well developed enough that they're pretty easy to program against and Claude/the AIs can pick up the API surface. Plus, people generally don't know what they're looking at -- you have to say "kindle-style screen" -- but people (me? but also guests) do seem to prefer having a e-ink screen in the living room over a backlit display because it's so much less intrusive.
FWIW, E-ink [0] AND pomdoros [1] are each a whole thing of mine.
Comment · 2 years ago
This is a good point. Seems like a likely candidate for an S curve in tech development. i.e. next 15 years of VR are improvements to camera, display, and tracking technology. Following 15 years are brain implants.
Comment · 3 years ago
I’m pretty sure Anders, Steve Lucco, and Daniel Rosenwasser worked on this. So inventors + current lead PM of typescript.
Should lend some credibility to the project.
Comment · 3 years ago
Even just an eye-test shows it's much faster than that for me.
Pagespeed shows .6 for desktop, but locally I'm seeing frames loaded under 350ms. I would have guessed much faster, but I guess the devtools don't lie.
Comment · 3 years ago
Really impressive stuff. Seems to have slowed down slightly now that it's on the front page, but blazing fast when I first opened it.
Comment · 3 years ago
I have really enjoyed learning from teachers and found "teachers" for fitness, language, and writing.
Has anyone found a teacher for something non-traditional or particularly interesting?
Comment · 3 years ago
All state including the app logic, UI, and app state of the component was shared/stored/synced via Fluid (I believe now Azure Fluid Relay.)
This simplified integration because each app only need to include a simple boot loader that could connect to the appropriate endpoint and then load every part of the component.
Comment · 3 years ago
While this does look like a clone of Notion and I'm frustrated this took SIX (!!) years to ship, I'm unbelievably proud to see this out in public. I was working on this in November of 2017, when we demoed collaborative canvases built with what's now the Fluid Framework to Satya. In fact, I turned down an early job with LimeBike after Steve Lucco let me demo a collaborative YouTube player to to BillG.
A huge congratulations to the team and amazing work on the product. I'm excited to see what comes next.
A few thoughts...
1. The Autonomous Agent/AI stuff has been deep in the Loop/Fluid Framework/Project Prague DNA since the beginning. The 2019 demos to the exec team included "Bindy" (Clippy's smarter sister), which was an intelligent agent that could live translate, spell check, insert content, and more. This demo [1] from Build 2019 includes some of that sauce with the live translate demo (and me back stage operating part of the Teams integration)
2. A huge part of the technical problems with Loop was building a secure launcher like OLE, that worked across Office on Web and Native. In fact, it seems like the M365 AI CoPilot is built on the same technology, which would make sense as you need a way to securely add another collaborator (the AI) and additional cross-plat & cross-app logic.
3. Working on cross app components like Loop and with CRDTs/OT really gets the imagination going. Especially because we were (at the time) very excited about 3rd party components like Asana, SalesForce, or Grammarly. Ideally these could be combined gracefully a la Semantic Web. It'd be so powerful to allow users to modify web pages, combine data sources, and generally own their own environment so they can design their own tools.
Geoffrey Litt recently summarized how AI could unlock this future [2]. I also spent time in crypto with the hope it could unlock this future (by incentivizing people to adopt shared protocols). Loop & Microsoft could also allow centralize enough developer mindshare to unlock part of this vision. (Perhaps more effectively than Code Packs?)
[1] https://www.youtube.com/watch?v=RMzXmkrlFNg
[2] https://twitter.com/geoffreylitt/status/1637592619269214209
Comment · 4 years ago
When I was working on this problem with Fluid Framework, we did a few interesting experiments with "owned objects" and centralized ACL objects. I believe the team primarily implemented centralized ACL because that implementation works for many enterprise use cases.
With a centralized schema provider, you run a connected node on a trusted server and reject changes that are out of schema or should not be accessed by a user.
An owned object is an object where a user (or user group that votes via quorum) that owns the object can veto changes to the object. The changes are temporarily applied until accepted by the owners. I haven't dug deep enough into this BFT implementation to know how our model would map to this model.