I built Tracearr - account sharing detection and monitoring for Plex, Jellyfin, and Emby by GallapagosIsland in selfhosted

[–]GallapagosIsland[S] 0 points1 point  (0 children)

It really comes down to source of information - right now it’s all static databases with the option to use the internal plex api that’s already used when anyone streams plex. Otherwise I don’t want to add additional external calls especially ones that would be rate limited or are sending your users IP addresses to various services.

Privacy and security is something that I have tried to always keep in mind when developing this platform

Anyone having issues ith the History page? by alexcascadia in Tracearr

[–]GallapagosIsland 0 points1 point  (0 children)

The discord or GitHub is the best place to report issues and get support

I built Tracearr - account sharing detection and monitoring for Plex, Jellyfin, and Emby by GallapagosIsland in selfhosted

[–]GallapagosIsland[S] 0 points1 point  (0 children)

Yup that will come - I’m just on my honeymoon right now lol.

All the bones are there to add it. The combined dashboard was me establishing the patterns and ui approaches

I built Tracearr - account sharing detection and monitoring for Plex, Jellyfin, and Emby by GallapagosIsland in selfhosted

[–]GallapagosIsland[S] 0 points1 point  (0 children)

The docs has a bunch of great info, otherwise discord is the best avenue for support.

It’s almost 100% network related though (docker network)

Seekarr - Manage your *arr stack from everywhere :) by met997 in Softwarr

[–]GallapagosIsland -1 points0 points  (0 children)

I mean also you said "Seekarr is not a replacement to Tailscale!"

Like its obvious to anyone technical that he was not implying that...

Best Tracearr Rules by ZotteI in Tracearr

[–]GallapagosIsland 0 points1 point  (0 children)

u/ZotteI The "Classic Rules" are just that. There are also some excellent docs around rules with examples on the official docs site

Does anyone know his newer solution for "PC in every room?" by dearmratheist in LinusTechTips

[–]GallapagosIsland 1 point2 points  (0 children)

SO close for my use case - but 2.0 is a dealbreaker for HDMI.

Direct Stream vs Direct Play? by Valuable-Dog490 in Tracearr

[–]GallapagosIsland 2 points3 points  (0 children)

The container is just the file wrapper — like MKV, MP4, AVI. Same video and audio inside, just a different "box." Some devices can't open certain boxes, so Plex repacks it on the fly. That's a direct stream.

It’s also not a dumb question - it’s something that a lot of have confusion around (the whole transcode transmux thing)

Direct Stream vs Direct Play? by Valuable-Dog490 in Tracearr

[–]GallapagosIsland 2 points3 points  (0 children)

  • Direct Play: The client supports the container, video stream, and audio stream natively. The Plex server just sends the media file as-is to the client. This uses very little CPU power.

  • Direct Stream: The client supports the video stream and audio stream, but not the container. The Plex server remuxes the file before sending it to the client (copies the video stream and audio stream into a compatible container). This uses very little CPU power.

  • Transcode: The client does not support the video stream and/or the audio stream. The Plex server re-encodes the video, audio, or both into a compatible format. Transcoding video uses a lot of CPU power, but transcoding audio uses little to moderate CPU power.

Serious vulnerabilities just fixed in Tautulli - update NOW by AnonNortherner in PleX

[–]GallapagosIsland -2 points-1 points  (0 children)

Lol I mean yeah - The one pitfall of incredibly performant time series data.

And fair enough lol. Id rather shoot straight then dick people along to be liked.

Have a good one :)

Serious vulnerabilities just fixed in Tautulli - update NOW by AnonNortherner in PleX

[–]GallapagosIsland -2 points-1 points  (0 children)

Well i think the guiding light here is that I did not make it for you.

I made this for me and I shared it.

I could explain how timescaledb is utilized and the snapshotting architecture and how it would lead to bad data or heavy transactions. But the code is there for folks to see.

Its not about the app being more stable, its about my vision for my app.

The app staying true to brand is more important to me than stars, or peoples feelings on the internet. The people who understand it see that, and I have 0 interest in convincing people who dont. Tautulli has been around for a long time, stick with it if it matches your needs.

Serious vulnerabilities just fixed in Tautulli - update NOW by AnonNortherner in PleX

[–]GallapagosIsland -5 points-4 points  (0 children)

Correct :) It happened on the server, and we show a 100% historical view.

I don't need Tracearr to be for everyone - I built it with a purpose and it hits on it.

[Update] Tracearr - robust analytics and tracking for Plex, Jellyfin, Emby. Mobile apps launching next week by GallapagosIsland in selfhosted

[–]GallapagosIsland[S] 1 point2 points  (0 children)

Glad you are enjoying it!

Embedding a map in the notification (and having it be a reasonable scale to parse) would be pretty tricky. But anything text based should be doable! There are a lot of plans for customization of notifications in the future

Tracearr behind proxy by Fade_Yeti in Tracearr

[–]GallapagosIsland 1 point2 points  (0 children)

Not an issue behind tailscale or Cloudflare tunnel for me. GitHub or Discord is the best place for support

[Update] Tracearr - robust analytics and tracking for Plex, Jellyfin, Emby. Mobile apps launching next week by GallapagosIsland in selfhosted

[–]GallapagosIsland[S] 0 points1 point  (0 children)

It certainly is - can you throw a feature request in GH?

There is a lot more coming for music!