PocketBase.io VS Block Protocol

Pocketbase [0] is a possibility. It offers a way to subscribe to collections, meaning the client will be notified if any of the records in that collection change. [1] Should be quite efficient too, the FAQ claims that 10k realtime connections on a small hetzner VPS is no problem [2] [0] https://pocketbase.io/. - Source: Hacker News / 9 days ago

I'd like to plug PocketBase [0] for a similar use case. Last week I was looking for a place to store random data with API access, and was looking at making a Google Sheets backend, but PocketBase was easy and didn't have a 60 rpm quota. Deploying to a cheap VPS was very easy with CapRover. [0] https://pocketbase.io/. - Source: Hacker News / 13 days ago

I wonder if it is inspired by [1], looks very similar including the "realtime" blurb. -- 1: https://pocketbase.io/. - Source: Hacker News / about 1 month ago

What is Pocketbase? Pocketbase is an open-source backend solution offering a real-time database, file storage, and seamless user authentication with OAuth integration, all readily available right out of the box. - Source: dev.to / 2 months ago

Browsing HN, GitHub and the like we get to see a huge variety of software products and code bases. I often see products and think - if this product X, got together with Y, it would be pretty cool - kind of like if they had a kid together. Not too literally, but more on the conceptual level - my level of programming is low. E.g. Just some.... - pocketable.io & datasette (+with some more charting)... - Source: Hacker News / 3 months ago

Off the top of my head… Tools for transclusion, inserting parts of other docs and rich references to them: https://en.wikipedia.org/wiki/Transclusion i.e. I refer to lobste.rs and Hacker news stories in posts like this: https://www.oilshell.org/blog/2021/04/build-ci-comments.html I wrote a bit of (offline) JavaScript to do it, but I could see it being expanded. I find it makes the posts more like a conversation... - Source: Hacker News / 4 months ago

Looks like that's using lit-html templates inside Svelte, but not any custom elements. Web components would be good because they're an interface that Primo could work with without relying on specific implementation details. They're also encapsulated with shadow DOM, and support interoperable composition (components can have child elements made from any other frameworks or library). So you could still build blocks... - Source: Hacker News / 9 months ago

Any chance this might interact with Block Protocol in any way? https://blockprotocol.org/ The obvious immediate benefit to this would be native editing of Wordpress blocks for your website. But if this became standardized and usable both locally and on the web, it could open up all sorts of interesting use cases. - Source: Hacker News / 10 months ago

I think the “servers” should be abstracted away from the user. Communities should be able to exist seamlessly across multiple servers, and the user shouldn’t need to know what servers a community is on. They should just be able to go to one website and access the entirety of the fediverse. Activities should adopt something similar to the Block protocol (https://blockprotocol.org/) so they can specify how they... Source: 10 months ago

The universal block thing...that's actually not too far from what is happening. WP didn't invent blocks, they adopted the Blocks Protocol. It's slow moving, with only a couple CMS's supporting it at the moment, but Drupal, Github, and Figma are planned to implement it as well. The idea being to enable a web standard for blocks that makes then platform agnostic. Use them anywhere on the web you like. Source: 10 months ago