JustinAngel

@[email protected]

This profile is from a federated server and may be incomplete. Browse more on the original instance.

JustinAngel,

Definitely complicated to root cause. Please share if ya figure out the hard parts 😄

An idea: Netflix could be fingerprinting TUN interfaces on the TV.

One thing I’d consider trying is Tailscale in userspace networking mode on a distinct network host at location 2, which’ll start a SOCKS/HTTP proxy that the TV can use for outbound connections.

Bonus: any devices incompatible with Tailscale can use the proxies.

If you’d like to take a stab at this, Headscale is a self-hosted version of Tailscale’s service. Personally, I use Caddy to automatically manage letsencrypt certs while proxying requests to Headscale.

JustinAngel, (edited )

Probably a poor decision to be creating accounts on government operated instances. Since they own the server, they’re in a position to:

  1. Siphon credentials and attempt reuse to gain access to distinct services
  2. Ban individual accounts
  3. Censor based on post content

I’m all for government support and adoption of open-source software so long as they’re not in the position to disrupt how it’s used by the public at large.

Edit (my perspective is relevant, but doesn’t apply in this case): My nerd impulses outran my willingness to read the link’s content. Seems it’s not for public registration.

Edit 2: Like my cornbread eating American ass can read Dutch anyway 🤣

JustinAngel,

My mistake.

JustinAngel,

My mistake.

JustinAngel,

Agreed, but we have to trust the instances we keep accounts on. Trust is subjective, but I certainly wouldn’t trust a government ran instance for anything other than an outlet for information originating from the owning government.

If I run a private instance or know the maintainer of another, then I can have greater confidence in the security/privacy implementations.

JustinAngel,

I’ve spent quite a bit of time as a penetration tester and one of the first things we do once we recover credentials is check for validity against online accounts known to be good for a given user. We do that because it simulates attackers and government operators alike. It’s a guarantee that free credentials will be abused in one manner or another when they’re available to government entities.

The obvious control for this is to maintain a unique password for each account but that’s not always feasible for users due to myriad conditions.

JustinAngel,

Would I trust them to not masquerade as me?..

Masquerading is literally the term used for this.

JustinAngel,

Just started learning about the fediverse but I suspect everything goes down with the ship. Sort of creates a development opportunity for community driven backup utilities, though. Interesting problems are fun development challenges :)

JustinAngel,

I just joined and I suspect that you’re correct: there’s an overall learning curve. No snarky tone intended, but explaining decentralization to those who would likely struggle with grasping the basic client/server model is going to be challenge.

Shoot, I’ve got 10 years pentesting and R&D under my belt and it took me a while to weigh the pros and cons of creating an account on a public instance or self-hosting. (Will self-host eventually…enjoying a test drive.)

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • uselessserver093
  • Food
  • aaaaaaacccccccce
  • test
  • CafeMeta
  • testmag
  • MUD
  • RhythmGameZone
  • RSS
  • dabs
  • KamenRider
  • Ask_kbincafe
  • TheResearchGuardian
  • KbinCafe
  • Socialism
  • oklahoma
  • SuperSentai
  • feritale
  • All magazines