Earlier quoted context omitted.
Yay! Registrations to https://merrilin.ai are open and you can enjoy a free account for as long as I can afford to give it (I have no funding lol). The android app is ready for closed testing too, if you have an Android device, mail me at mail [at] stonecharioteer.com and I'll add you to the beta testing. ios is still a pain.
Why don't you do sign in with openrouter oauth, then users can create an account and assign a key to your app, with spending limits. It's trivial, plus if you get a decent amount of users your app will appear on the leader board and that's free marketing for your project. https://openrouter.ai/docs/guides/overview/auth/oauth
Your ePub Is fine
201–210 of 322 posts
Re: Your ePub Is fine
#202Earlier quoted context omitted.
Why don't you do sign in with openrouter oauth, then users can create an account and assign a key to your app, with spending limits. It's trivial, plus if you get a decent amount of users your app will appear on the leader board and that's free marketing for your project. https://openrouter.ai/docs/guides/overview/auth/oauth
That's a good point, but our harness right now is very fine tuned towards kimi2.6, it's something we want to improve but it's just 2 broke dudes working on it right now.
Re: Your ePub Is fine
#203Re: Your ePub Is fine
#204Unfortunately, epub and epubcheck isn't the great uncontroversial resource the author makes it out to be. When W3C, Inc. took over maintenance of the EPub spec around when 3.1 was current, they just referenced WHATWG HTML and other ever-expanding browser specs ([1]). Being "living standards", these have no versioning or QA. As a consequence of being based on a version of HTML that redefined headers and sectioning, Ep…
Yes, it is widely known in the epub space that targeting 3.1 or 2 is the more sane option. With EPUB compatibility issues CSS should always be suspect number 1. Using "modern" CSS features and complaining about missing flex boxz grid, etc is a web developer's mindset. Just because EPUB shares some of the stack with the web doesn't mean they perfectly overlap (or even should). Hardly any e-ink embedded e-reader device…
Re: Your ePub Is fine
#205Earlier quoted context omitted.
Flash is still unsurpassed as the easiest publishing medium. JavaScript build system layer cake and "web standards" are a million times harder than just drawing some stuff, maybe writing a simple function, then building a static file that can be embedded anywhere and even downloaded. You have to spend so much time setting up any flash alternative, and the "standards" are worse. I hate Steve Jobs for killing Flash and…
You'll get hammered for this on HN, but the web was magical and weird with Flash around, and now it feels quite vanilla and boring. I long for the days of weird experimental art and goofy animations and bonkers UIs.
Re: Your ePub Is fine
#206Earlier quoted context omitted.
Flash had many issues for sure, first and foremost security. But I can’t help but feel sad of what was lost since then. The Flash era produced some really unique experiences on the web.
it was about as unique as seeing corn in my poop sometimes.
Re: Your ePub Is fine
#207Every Kobo reader is capable of running KoReader ( http://koreader.rocks/ ). That's the first, and probably last, step I'd take to render a book that the default reader takes issue with.
As I understand it, KoReader doesn’t work with drm protected books which means I can’t use it with most books I buy. Ebook producers really should be forced to either drop drm or adopt a cross-platform standard.
The publishing industry never got its head out of... some dark place. We've been able to buy mp3s without drm for ages, but somehow books are different.
Re: Your ePub Is fine
#208Re: Your ePub Is fine
#209Unfortunately, epub and epubcheck isn't the great uncontroversial resource the author makes it out to be. When W3C, Inc. took over maintenance of the EPub spec around when 3.1 was current, they just referenced WHATWG HTML and other ever-expanding browser specs ([1]). Being "living standards", these have no versioning or QA. As a consequence of being based on a version of HTML that redefined headers and sectioning, Ep…
Yes, it is widely known in the epub space that targeting 3.1 or 2 is the more sane option. With EPUB compatibility issues CSS should always be suspect number 1. Using "modern" CSS features and complaining about missing flex boxz grid, etc is a web developer's mindset. Just because EPUB shares some of the stack with the web doesn't mean they perfectly overlap (or even should). Hardly any e-ink embedded e-reader device…
Re: Your ePub Is fine
#210BTW for those who are looking for a device, the PineNote exists: https://pine64.org/devices/pinenote/ More expensive and less out-of-the-box software, but straight to the point on device ownership/what kind of software you can run, fewer strings attached. [EDIT] Great experience blogs on the PineNote https://shom.dev/posts/20250308_pinenote-day-one/ https://shom.dev/posts/20250406_a-pinenote-only-5-day-weeken...
The Pine projects are necessary and well-motivated, but the PineNote doesn’t strike me as a reader’s device, maybe a hacker’s or someone that wants an e-ink tablet.