[–] 2 points 1 month ago* (last edited 1 month ago)

Aaah! Oh. Yes that makes a lot of sense indeed.

The UX (and architecture, for that matter) of the dustbuilder has been.. uh.. lacking.. due to the lack of refactoring. It evolved over all these years, and things that had a meaning once suddenly gained a different one, but are still named in the old ways.

Good point, thanks for pointing it out! I've been doing some refactoring there, actually, and there, it's named "disable cloud", but I just did that for correctness. It did not occur to me that from a user-perspective, this is not just weird but actively misleading. I mean it kinda did, but I did not make the mental connection to this specific misconception. Oh well.

  • source
  • parent
  • context
  • [–] 2 points 1 month ago* (last edited 1 month ago) (2 children)

    It’s just DNS based, and iirc dont require any major effort other than patching the hosts file.

    Incorrect. That was technically sorta the case back on the S5 (and even there it needed firmware modifications), yes, but if DNS redirection was all it needs, then why even root the bots in the first place. Just do that on a network level and be done with it.

  • source
  • parent
  • context
  • [–] 1 point 1 month ago (3 children)

    It’d be a pretty big feature to implement, and surely it would be something that the Valetudo author would mention in the docs for the project.

    Dude. What?

    It is literally the only feature of Valetudo.

    Wat.

    What else would Valetudo possibly be doing other than disconnecting from the cloud?

  • source
  • parent
  • context