synestine

@synestine@sh.itjust.works

• ⁨Comment⁩ on ⁨Sharing Jellyfin⁩ ⁨⁨1⁩ ⁨day⁩ ago⁩:

  Ah, so you’re the kind who loves bitching about things online, but won’t lift a finger to defend themself, gotcha.

  What I mentioned prior doesn’t change anything about library management in the slightest, you just wanted an excuse.

• ⁨Comment⁩ on ⁨Sharing Jellyfin⁩ ⁨⁨4⁩ ⁨days⁩ ago⁩:

  The reverse proxy is the part that’s exposed. CrowdSec watches the logs for intrusion attempts like fail2ban would.

• ⁨Comment⁩ on ⁨Sharing Jellyfin⁩ ⁨⁨4⁩ ⁨days⁩ ago⁩:

  If you’re worried about it, make sure to not use a default path. Then legit clients are fine but these theoretical attackers get stymied.

• ⁨Comment⁩ on ⁨The Pebble Has Been Brought Back⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  Dozens? Name three, and be sure to include number of aps in each ecosystem.

  I’m sure there are dozens of Chinese smart watches, but most that I’ve seen are white-labels and sorely missing an ecosystem.

• ⁨Comment⁩ on ⁨The Pebble Has Been Brought Back⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  Methinks you underestimate the complexity.

  And all the other watch makers I’ve looked at are not doing, or even considering, what Pebble did.

• ⁨Comment⁩ on ⁨The Pebble Has Been Brought Back⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  Because good software is hard. The PebbleOS is a gem, and no, no one could in 9 years.

• ⁨Comment⁩ on ⁨The Pebble Has Been Brought Back⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  Google dumped the Pebble OS code on GitHub when this whole “rePebble” thing (not Rebble) started. Now there’s a new phone app coming out soon (or out now, depending on your platform and abilities) that handles old and new Pebbles and modern phone platforms.

  None of this is from Google.