From left to right:

• TWSBI Diamond Mini Classic 1.1mm stub nib
• Pelikan 140 M(?) nib
• Unknown Kondor pen
• Lamy CP1 F nib
• Lamy joy 1.5mm stub nib

The TWSBI is the only pen in this collection that I actually bought. The rest came into my possession through family and as such are mostly older pens.

The Pelikan 140 is by far the oldest and my current favorite alongside the TWSBI. From what I've been able to find, this one was manufactured somewhere between 1955-1963. It is also the only pen in my collection with an actual gold nib.

The Kondor, just like the TWSBI and Pelikan is a piston filler and has a in my opinion strangely shaped nib. It is slightly scratchy unfortunately.

The Lamy CP1 is the pen that I used the longest out of all of these and was my daily driver during my later school years. Back then I had an M nib on it which I later switched for an F. Despite it being a beatufil sleek pen, I rarely use it anymore since the grip section tends to accumulate some ink near the front. This combined with my very close grib means that I always get ink on my fingers when writing with it. I am not sure if this is a defect of my specific pen or is something that has been fixed in newer models as this pen is apparently also quite old, based on the "Made in W. Germany" inscription under the clip. This pen also tends to be kind of unwieldy when used with the cap posted, as the cap is made of a much heavier metal than the rest of the pen, making it unbalanced.

The Lamy joy is a pen I briefly tried but found to have a much too thick nib for my daily use. Compared to the TWSBI it is also kind of scratchy.

Hello everyone, I have another question regarding reverse-proxying again, specifically for the linuxserver.io jellyfin image.

On the dockerhub page for this image there are 4 ports listed which should be exposed:

• 8096 for the HTTP Web UI
• 8920 for the HTTPS Web UI
• 7359/udp for autodiscovery of jellyfin from clients
• 1900/udp for service discovery from DLNA and clients

Additionally there is also an environment variable JELLYFIN_PublishedServerUrl which is for "Setting the autodiscovery response domain or IP address". I currently have that set to my subdomain https://jellyfin.mydomain.com though I am not sure if that is correct.

I already have a reverse-proxy set up allowing me to access my servers webinterface under https://jellyfin.mydomain.com without exposing the https port on the container. What I am unsure about now however, is what to do with the two ports for UDP traffic.

By my understanding, a reverse-proxy will only forward traffic which comes to the ports 80 for http and 443 for https. Those are also the only ports my reverse-proxy container has exposed alongside the management interface. As such the 2 udp ports will not be reachable under my jellyfin domain.

How can I change this or is this even an issue?

Hello, I have a question regarding the usage of a reverse-proxy which is part of a docker network.

I currently use Nginx Proxy Manager as a reverse-proxy for all my services hosted in docker. This works great since I can simply forward using each containers name. I have some services however (e.g. homeassistant) which are hosted separately in a VM or using docker on another device.

Is it possible to use the same reverse-proxy for those services as well? I haven't found a way to forward to hosts outside of the proxies docker network (except for using the host network setting which I would like to avoid)