On 18. Dec 2020, at 0:31, colecmac at protonmail.com wrote: >> I think the primary advantage of this bookmarks .gmi format would be interchange >> between clients (and instances of the same client) without humans editing the file. >> I don't think a client would want to store their bookmarks in this format, as there >> may be additional (possible internal) metadata to deal with, too. > > Well, that works for me. Amfora already has support for file:// URIs in master, so > in the next release you'll be able to just open any gemtext file and use it as your > free-form bookmarks. Great! I've also added support for using bookmark .gmi files/pages in Lagrange (v1.0). On 15. Dec 2020, at 23:08, C?me Chilliet <come at chilliet.eu> wrote: > I?ve put together an idea of simple specification to allow clients to synchronize bookmarks and feeds across Gemini, as this is something that I?m currently missing in my daily Gemini use. > * Would you consider implementing support for something like this? I'm changing my previous answer now with Lagrange v1.0 having support for remote bookmarks. It solves 80% of the problem, especially if you throw in Dropbox/etc. to sync your bookmark files across devices, or get them via your existing Gemini server. So what remains is automated upload of added/deleted bookmarks, and for that it seems setting up a custom server might be overkill. The UX benefits of automation are still there, but maybe there is something even simpler that could do the trick. I'll give it some thought. --jaakko
---
Previous in thread (13 of 14): 🗣️ colecmac (a) protonmail.com (colecmac (a) protonmail.com)