Feedback wanted: tell me where this breaks, where it's unclear, and what you'd use it for

[DiegoGuidaF]

Thanks for checking out PulseWeaver. This thread is the place for first impressions, questions,
and ideas — use Discussions for feedback, Issues for concrete bugs.

A quick reminder on what this actually is, since it's the most common thing to misread:
PulseWeaver is not authentication. It gates requests by IP + host so unknown visitors never
reach your apps — but it doesn't verify who someone is. Keep your services' own logins on. If
anything in the README or docs made that unclear, that's exactly the kind of thing I want to hear
about here.

Two things I'd love your take on:

1. What's confusing or missing? Docs, terminology, the setup flow, the "shared IP" caveats —
   if something made you stop and re-read, say so. Rough edges are easiest to fix early.
2. What would you put behind this? Jellyfin for a friend is the README example, but I'm
   curious what real services/use cases you're thinking of — it shapes what gets prioritized next
   (iOS client, more reverse proxies, more features, etc.).

I have a list of new features & ideas to work on however I decided this was a good point to stop, publish it to the community and gather feedback.

[HGGamers]

Anyone else getting unauthorized when trying to pull ghcr.io/diegoguidaf/pulseweaver:latest? Seems like the ghcr package might be set to private.

Error response from daemon: Head "https://ghcr.io/v2/diegoguidaf/pulseweaver/manifests/latest": unauthorized

[DiegoGuidaF]

Though those would become public when the repository went public. FIxed!