@skyjake any chance of adding a feature to allow adding posts to a favorites/read later/bookmark type list?

Posted in: s/Bubble

🐐 drh3xx

Feb 13 · 3 months ago

7 Comments ↓

🕹️ skyjake [mod...] · Feb 13 at 13:29:

It seems this would duplicate client-side bookmarking functionality, but I guess the advantage would be having the bookmarks/favorites "in the cloud" so if one uses multiple clients, syncing wouldn't be an issue. I'll need to think on this a bit.

Note that you can use the "Remind me" notifications for this purpose, kind of.

👻 mediocregopher [...] · Feb 13 at 16:32:

I wasn't asked but agreed, a higher level solution could be to work on some kind of standard bookmark (and identity?) syncing mechanism that browsers can use. Such a thing already mostly exists for http browsers via WebDAV (see floccus).

🐐 satch · Feb 13 at 17:54:

I would make use of this feature within BBS. I don't want lots of bookmarks cluttering up my list outside of BBS, I have different uses for them.

🚀 stack · Feb 14 at 01:39:

Agreed. I'd love to bookmark within BBS as I access it with 4 different devices.

🐐 drh3xx [OP] · Feb 14 at 13:45:

@satch that was pretty much my motivation for the request. @stack this is my situation too. I've not found a good way to sync bookmarks and identities in Lagrange across several devices yet. I know you can source bookmarks from a remote gemini source but there doesn't appear to be a good way to add to that source from the client.

🚀 stack · Feb 14 at 18:13:

@drh3xx: I, too, tried to use a remote bookmark solution, but these bookmarks are very different from normal ones - you can't even move them around or delete them, or get them back out. I get that Lagrange can't modify a read-only source, but it would be nice to be able to edit them in Lagrange and export them, and manually close the loop.

🕹️ skyjake [mod...] · Feb 14 at 19:26:

The Lagrange remote bookmark feature could use a little improvement. It also has some bugs when it comes to converting remote ones to local bookmarks...

Bookmark syncing would be nice, however as it requires a server component somewhere it gets somewhat complicated. I think there is a GitHub issue about that with some discussion.