Bookmark Module

[ElHado]

Hi,

thanks for your great work. Maybe a shared (and personal) bookmark library would be great. Maybe you could connect to Readeck or something similar or a own, simple bookmarking tool for the whole family.

Greetings Dominik

[ulsklyc]

Thank you - and this pairs with #469, where the request arrived from the other end: a family that uses Yuvomi as its home page wanting the links to Jellyfin and friends to be right there on the overview. Same data, different ambition, so I would rather decide them together than build one and discover it was the wrong half.

Nothing stores a link as a first-class object today. A note can hold URLs, but a note is prose - it will not give you a launcher, and it will not give you a library either.

Where the two split: a short list of household links on the overview is a widget - name, URL, icon, and who may see it. A bookmark library with collections, tags and a personal/shared split is a module, and it lands in territory where dedicated tools (Readeck, Linkding, Hoarder) are already better than anything a family planner would grow on the side.

That is also why I am wary of the integration idea specifically. Yuvomi's existing integrations - Mealie, Tandoor, CalDAV - read from systems the household already runs. A Readeck bridge would fit that pattern, but it only helps the households that already run Readeck, which is a much smaller set than the ones who would use three links on the overview.

Staying open. Would the personal/shared distinction be the point for you, or is it mainly having the family's links in one findable place?

[ElHado]

Hi,

I already use Readeck, thats why I mentioned it. But if I think about it then Readeck is much more I need in Yuvomi. It was a bad example, sorry for that. We would need a place to share some links, this can be a module or a widget in the overview. It is really only about links, we don't need the whole article behind or something like that. Only link, maybe a nice icon (uploadable would be great) and who can see each link, thats it. So I think for me we can stay with #469

[ulsklyc]

That settles it, and it settles it in the useful direction - thank you for saying so plainly.

So the shape is agreed from both ends now. You came at it wanting a library and concluded a shared list of links is what you actually need; #469 came at it wanting a launcher and arrived at the same place. radicchiodev put the constraint on it that matters most: no predefined app list. Name, URL, icon, who sees it. Anything tied to a catalogue of known services is wrong the day someone runs a service that is not in it.

Your addition of an uploadable icon is worth keeping - a favicon fetch would mean the household reaching out to every linked host, which is exactly the kind of quiet outbound traffic this app avoids. An upload keeps it local.

I am consolidating into #469 so the requirement lives in one place instead of two half-specifications. Closing this one as resolved - not as declined. The feature is the one you described; it just has a different number.