Skip to content

[Feature Request] Public profile #88

Description

@codebude

Quoted from @DawidGardzinski in the original issue Feedback after 1-2 weeks of using Libris (#78).

It would be great if there were a way to share your profile with someone so they could browse it!


Author: @DawidGardzinski
Original issue: #78

Activity

  1. codebude commented on Sep 4, 2026

    @codebude
    OwnerAuthor

    That's a cool idea. Before we get into the content of such a profile, we'd need to think about it architecturally. Librislog is self-hosted by its users. So if we implement the share page locally in Librislog, it's only reachable within the network where the Librislog instance is reachable. That means: if a user's Librislog instance is only on their LAN, friends in the same LAN could view the profile. To share it with the world, each operator would then have to make sure the page/path gets routed to the internet. Would that be a solution in your interest?

    Alternatively, we'd need to implement a central service that I, for example, could host on one of my servers. Librislog would then only feed profile information to that server, and the server – sitting on the internet – would serve the profile pages. That way Librislog instances could stay protected in private networks, while users could still host public profiles they can post on the internet. However, that would mean user data goes to an external service. I'm not sure whether that's in line with the self-hosted community. We'd probably need to include a big disclaimer here.

    Which solution did you have in mind?

    @DawidGardzinski Just adding you here so you see my reply – looking forward to your take on this.

  2. DawidGardzinski commented on Sep 5, 2026

    @DawidGardzinski

    I had the first, fully self-hosted approach in mind.

    I think it would be best if Librislog simply provided a public/shareable profile page locally, and it was up to the instance operator to decide whether and how to expose it to the internet - for example through a reverse proxy, tunnel, VPN, or only within their LAN.

    That keeps Librislog independent of any central service and avoids sending profile data to a third party. Users who want a publicly accessible profile can configure that themselves, while users who want to keep everything private don't need to change anything.

    A central hosted service could perhaps be an optional solution later, but personally I'd prefer the core feature to remain completely self-hosted.

  3. self-assigned this
    on Sep 9, 2026
  4. codebude commented on Sep 10, 2026

    @codebude
    OwnerAuthor

    @DawidGardzinski profile functionality was implemented in #101. I would love to get your feedback.

  5. DawidGardzinski commented on Sep 11, 2026

    @DawidGardzinski

    looks great:

    Image

    tiny issue:

    Image

    link is barely visible on dark theme

    Image

    spaces between elements are too small

  6. codebude commented on Sep 11, 2026

    @codebude
    OwnerAuthor

    I'll put your feedback to my todo list. Thus I'll open the issue again.

  7. codebude commented on Sep 13, 2026

    @codebude
    OwnerAuthor

    I raised contrast by changed colors and added some spacing in #103

    Image Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions