Nick The Sick

Nick The Sick

@nickthesick.com

I write many codes @ https://blocknotejs.org Working on @bookhive.buzz and @teleportal.tools github.com/nperez0111 Read my blog at nickthesick.com Support me on Ko-Fi: https://ko-fi.com/nick_the_sick

694 followers452 following1.3K posts

It's always felt strange to me that "Copyright" is about denying the right to copy. There are infinite facts, finding useful ones doesn't make them yours. I'd rather have my ideas spread than extract value out of them.

P(aul) Frazee@pfrazee.com

I'm a free information radical. I have spent most of my career publishing open-source code and building open-information systems. I grew up getting access to knowledge that I never would've otherwise had because of the Internet. The past 5 years have accelerated it. I think the future is bright.

I’d love feedback on this! github.com/nperez0111/b...

github.combook.lexicon.community proposal by nperez0111 · Pull Request #229 · nperez0111/bookhiveThis is a proposal for the specific community.lexicon.book.* lexicons. It is based on the following articles: https://nick-the-sick.pckt.blog/road-to-a-book-lexicon-part-1-t2eyqge https://nick-the...
Lexicon Community@lexicon.community

Book WG momentum: @nickthesick.com submitted a PR on BookHive with proposed lexicons for book editions and standalone reviews — splitting edition data from reviews into distinct namespaces. The path to community.lexicon.* publishing: a Tangled registry PR is next. Join the discussion.

I think what is happening with PNPM is similar to what happened with Redis. Most people only ever use Redis as a KV cache, and then when they decided to change license, everyone freaked out because they rightly only need 1% of what Redis does.

By adding to your open source project rather than differentiating it with another product, you are offering the full value to someone and feel wronged when they don't reward you for it, but the reality is that they only ever needed the one thing - the package manager.

Don't worry guys, Part 2 is here: Houston, we've got a book & review lexicon! I don't think it is in it's final shape just yet, but I believe it to be a strong proposal, and well justified if I may say so, myself 😌

nick-the-sick.pckt.blogRoad to a book lexicon (Part 2)The one where I actually define a lexicon
Nick The Sick@nickthesick.com

I've been thinking a lot about how to define a shared book lexicon for the Lexicon Community Working Group: discourse.atmosphere.community/t/in-which-a... But, instead wrote a treatise against ISBNs. I hope I can link to it whenever someone asks why their import didn't work on @bookhive.buzz 😝

In a similar sort of vein, I’ve been thinking about a separate S3-like storage solution for atproto. Like what would it take to have a decentralized hook up your own storage system for applications with much more data than what you’d want to put in a PDS. Imagine Google Photos scale

Matt Kane@mk.gg

Meet ☁️ Cumulus: an atproto blob proxy on Cloudflare Workers Cache. Supports Bluesky-compatible image resizing, mimetype filtering, CID verification. Run a lexicon-scoped instance just for your app. Subscribes to labelers to purge account and record !takedowns.

I'm looking at how to get to @zurichjs.com & just out of curiosity wanted to see the difference between the trains I was looking at, compared to a flight. It costs more to go by train & takes 9h for a 1.5h flight 🙄 We've got our priorities straight huh?

live in: 🇳🇱 born in: 🇺🇸 parents: 🇺🇸🇨🇺 grandparents: 🇵🇷🇵🇷🇨🇺🇨🇺 great grandparents: 🇵🇷🇵🇷🇵🇷🇵🇷🇨🇺🇨🇺🇨🇺🇨🇺 been to: 🇺🇸🇨🇺🇯🇲🇭🇹🇧🇸🇩🇴🇲🇽🇨🇷🇪🇨🇨🇦🇪🇸🇳🇱🇹🇷🇱🇺🇧🇪🇩🇪🇫🇷🇮🇹🇨🇭🇬🇧🇩🇰

Scan@scanash.com

live in: 🇺🇸 born in: 🇨🇺 parents: 🇨🇺🇨🇺 grandparents: 🇨🇺🇨🇺🇨🇺🇨🇺 great grandparents: 🇨🇺🇨🇺🇨🇺🇨🇺🇪🇸🇪🇸🇪🇸🇪🇸 been to: 🇨🇺🇬🇾(us embassy :D)🇺🇸 im planning on going to spain soon

I added a KOSync server to BookHive, which allows synchronizing reading progress across your e-readers. It's based on my existing: kosync.nickthesick.com But, I've added OPDS support which means BookHive can store your ebooks and serve them to your e-readers too.

BookHive@bookhive.buzz

BookHive now syncs with your e-reader. Upload your ebooks, browse them from KOReader, Crosspoint, or Readest, via OPDS, and your reading progress syncs back into BookHive.

View full thread

Similarly, OPDS is implemented in the same sort of way, where the user can store ebooks to BookHive, and the only way to access them is through the username and password. The user can organize the books into "shelves" which will show as separate OPDS folders in the e-reader.

I added a KOSync server to BookHive, which allows synchronizing reading progress across your e-readers. It's based on my existing: kosync.nickthesick.com But, I've added OPDS support which means BookHive can store your ebooks and serve them to your e-readers too.

BookHive@bookhive.buzz

BookHive now syncs with your e-reader. Upload your ebooks, browse them from KOReader, Crosspoint, or Readest, via OPDS, and your reading progress syncs back into BookHive.

View full thread

BookHive now acts as a KOSync server and uses your handle as the username, and a generated password for your account (which you can rotate if you need to). It uses this username & password for both KOSync and OPDS.

When a user pushes progress it updates their BookHive record if they have linked which book they want to push it to. Otherwise, it stores it locally in the BookHive DB. If there is interest, I can add a lexicon for this to be public, but for now it is private.

I added a KOSync server to BookHive, which allows synchronizing reading progress across your e-readers. It's based on my existing: kosync.nickthesick.com But, I've added OPDS support which means BookHive can store your ebooks and serve them to your e-readers too.

BookHive@bookhive.buzz

BookHive now syncs with your e-reader. Upload your ebooks, browse them from KOReader, Crosspoint, or Readest, via OPDS, and your reading progress syncs back into BookHive.

I added a KOSync server to BookHive, which allows synchronizing reading progress across your e-readers. It's based on my existing: kosync.nickthesick.com But, I've added OPDS support which means BookHive can store your ebooks and serve them to your e-readers too.

BookHive@bookhive.buzz

BookHive now syncs with your e-reader. Upload your ebooks, browse them from KOReader, Crosspoint, or Readest, via OPDS, and your reading progress syncs back into BookHive.

I was thinking of going a step further and making a KOReader plugin specifically for BookHive, but I'm unsure that I really need it right now. Though, I could get a lot more information than just synchronizing progress between devices if I were to integrate it.

I've just added this to @bookhive.buzz!

𝕮@chrisshank.com

In the *last day*, a bunch of apps in the Atmosphere are starting to adopt this proposal! Thanks to everyone who has helped out 🙏🏻 - @mu.social ☑ - @semble.so ☑ - @aturi.to ☑ - @leaflet.pub ☑ - @frontpage.fyi ☑ - @bsky.app ☐ - @pckt.blog ☐ (just reached out)

Nick The Sick reposted

this year i've carved a big chunk of my time out to officially work on OSS. if you like what I do, or use the things I work on, sponsorships go a long way. these help me keep the balance I have, and allow me to dedicate a lot more time to open source. thank you to those who already sponsor me 💙

github.comSponsor @43081j on GitHub SponsorsMaintainer of clack, chai, parse5, unjs, vueuse, tinylibs, & more. One of the e18e.dev leads. Core contributor to lit and modernweb.

Portainer is a self-hosted docker manager that I use to deploy all of my self hosted services. I’ve just hooked up its MCP server and it is awesome to have completed the loop on an agent managing all of my self hosted services. It can diagnose issues end to end and redeploy.

Hooking up an agent to something which has versioning built-in inspires much more confidence in being able to manage something like this. I always have the safety to roll back if I need to