Benefits of open-sourcing Yakread
# forum
j
Copied from #958102014733189191 (continuing here since I wrote up a long response): > @erlend > Also, does yakread intend to remain closed source? I’d feel a lot more comfortable using it if it was source-available. There are licenses that keep your IP and business interests protected, whilst giving users the significant value-add of source code access: https://polyformproject.org/licenses/noncommercial/1.0.0/ > > @Jacob O'Bryant > The plan currently is to remain closed source. I'm open to the idea of going open-source or otherwise releasing the code, but I'd want to make sure it's in best interest of the business (or that I have an income from somewhere else), and it's still at such an early stage right now that I wouldn't want to make any promises. > > In general I do try to be transparent and avoid lock-in. What are the benefits of releasing the code that you're most interested in? (e.g. would you want the option of running a personal self-hosted instance? or would you just want to audit the code's data/privacy handling/ranking algorithm?) > > @erlend > Benefits include: > - Less lock-in > - Greater capabilities for modding > - Trustworthy algorithms > - Better bus-factor (project can still be maintained if solo-founder disappears) šŸ‘ I'll let you know if I do end up open-sourcing it. Again I wouldn't want to make any prognostications unless I start getting an income from somewhere else, e.g. if I were to get more corporate sponsors for my open-source work. But in the mean time:
> - Less lock-in You can export your data on the settings page, including an opml file for your RSS subscriptions (and bookmarks + reading history). For newsletter subscriptions I recommend signing up with your regular address (e.g. alice+sub@example.com) and setting up a filter to forward emails to your @yakread.com address. I started doing that myself a while before building Yakread, so switching the newsletters to it was easy--just update the filter's forward destination. At some point I'd like to provide email forwarding from Yakread, and/or possibly create an RSS subscription for each of your newsletter subs, so they can be included in the OPML export. > - Greater capabilities for modding > - Trustworthy algorithms I would like to make the ranking algorithm pluggable. I've played around with Fly Machines (https://fly.io/blog/fly-machines/) and I think that could work well--i.e. you create a Dockerfile for a service that receives a list of items with various metadata, then return a sort order. You upload the Dockerfile, then Yakread handles the rest. If I do this, I'd convert the default algorithm to such a Dockerfile and open-source that. See also https://discord.com/channels/806901242290241578/1033496881780768909/threads/1034198629239496724. I've also written a couple articles (https://tfos.co/p/timelines/, https://tfos.co/p/designing-the-timeline/) that give a high-level explanation of how the algorithm works. I'm planning to publish more explanations like that if/as I make significant modifications to the algorithm. Maybe add a single "how the algorithm works" page and keep it up-to-date. Finally, I'd like to make the data import integrations more extensible. At a minimum, perhaps support RSS for importing bookmarks + social posts. Maybe add an API. Doing something fancy with Fly Machines might be an option too, so you could write some code to fetch data from other services and let Yakread handle the deployment.
All this stuff is contingent on hitting profitability with the business first. > - Better bus-factor (project can still be maintained if solo-founder disappears) Current plan is to hire more people after the business is profitable; remaining a solo-founder isn't really a priority for me. I'll tell my wife to release the code if the bus does become a factor in the mean time šŸ™‚ .