Now that #omnivore is dead and folks struggle to selfhost it, I should probably polish my own read-it-later app and make it open source?
https://phpc.social/@stefanzweifel/110906465364853219
Written in PHP makes it simple to host. All the advanced features like text-to-speech or content-extraction are driver based and not tied to a specific cloud.
If you don't like GCP, just provide AWS credentials and use that text-to-speech API.
But do I really want all that maintenance burden? 😅
Support highlights and iOS apps?
=> More informations about this toot | More toots from stefanzweifel@phpc.social
@stefanzweifel If it has an API you don’t really need an iOS app, shortcuts can handle it.
=> More informations about this toot | More toots from robb@social.lol
@robb True. I plan to add a REST-API for everything the app can do. So technically others could build native apps, if they want one.
=> More informations about this toot | More toots from stefanzweifel@phpc.social
@stefanzweifel Been wanting to open-source my own feed reader (until I effectively stopped using it ☹️).
Now investigating merging it into my (already open-source) CMS.
Despite it being a feed reader first and foremost, it supported having individual (i.e., non-feed) pages added to it for reading at a later time, via Micropub requests (an idea I stole from @aaronpk’s Aperture feed aggregator).
=> More informations about this toot | More toots from janboddez@indieweb.social
@stefanzweifel or you can also contribute with us to @wallabag ?
=> More informations about this toot | More toots from nicosomb@piaille.fr
@nicosomb @wallabag That would also be an option. :)
=> More informations about this toot | More toots from stefanzweifel@phpc.social
@stefanzweifel wait what happened to Omnivore?
=> More informations about this toot | More toots from sven@phpc.social This content has been proxied by September (3851b).Proxy Information
text/gemini