• 0 Posts
  • 29 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle
  • In general if people are genuinely hurt by the use of some words, I’m not sadistic so I’ll avoid using them

    That’s a sane position. Only issue is that this have nothing to do with the question, and the people that were the most vocal about this issue had no business talking about it in the first place.

    Ultimately, git is flexible; beyond some potential local and shared automation, anyone can call their local branches however they want, regardless of other and servers. Personally, changing years of habits and tooling (that probably should not have hardcoded some names in the first place) is not worth following a change proposed by misled people.



  • So-called “social” networks can have three main issues: technical (they have to work), leadership (they have to not be dickhead), and users (they also have to not be dickheads).

    The first point can be handled with competent people, consensus, open source contributors, etc. (assuming no dictatorial management).

    The second point can probably be handled by having a handful of decent people, transparency, accountability.

    The third point, which is basically the thing that makes the content on the service… is still people. If people were obnoxious on twitter, they’ll be obnoxious on bluesky, mastodon, and whatever else shows up. It’s almost inevitable.

    It’s also why decent moderations tools are needed, which brings the question of how to do decent moderations tools that are not too extremet but still remains useful. This is not an easy task (and to my knowledge, there’s no general solution to that).

    Bots showing up is just the icing on the top. Without a pretty aggressive vetting system for accounts, there’s not much that can be done from the service itself.

    Given the general ambiance, I guess smaller community and services tailored for them might come back, the way we had tons of different forums back in the days. It might be a good solution; some form of SSO across many services to make people reachable, but no general, shared stream of messages as we have now.

    tl;dr: it’s not a technical problem, it’s a people problem. So it won’t be solved by technical solutions.




  • I’m worried about anything that can be controlled through a third-party online service. The amazon doorbell thing is a prime example of what can go wrong, but it can be more subtle, too. And I’m not even talking about obsolescence. Frankly, I’d still be worried if it was a self-hosted, properly configured system where I’m the only one with a legit access.

    I understand the convenience of all this. I also have to deal with the risk balance of security vs convenience, which causes me to not tolerate that “too tired to go across the room” justifies “a third party have full control over my doors, lights, heating, ovens, etc.” (not shooting fire at you, see this as a generic example).

    The bare minimum would be a fully self-hosted solution, which is possible, although difficult because hardware manufacturers don’t always play nice. And even then, proper, secure setup and maintenance is not for everyone. In the meantime, yeah, I’ll have to move myself when I want to turn on my dishwasher.

    Though I’ll admit, I have some lights that are controlled wirelessly… my old phone have an IR port, and they have IR remotes… Technically, an attacker could probably turn them on/off/change colors from behind a window :D


  • I’m warry of electronic, wireless, and sometimes third-party cloud dependent services, having a say in how I lock my doors or control heating.

    I’m a bit old fashioned, but also have to work with solutions where considering the consequences of a compromised entry point is vital. I’d be ok with a way to check that the door is locked, but something that can lock (and, so, unlock) my door remotely? Not a chance. At least, not for a place a value.










  • The label for the language picker is an issue, but the choices themselves? In the target language. You want French? You pick “Français”. You want Japanese? You pick “日本語”. You want english? You pick “English”.

    Supposedly, if you’d rather have a website in a given language, you must have some level of understanding of that language, and picking its name should not be a challenge in any case. If you somehow change a site/app to a language you don’t know, as long as you can identify the language picker, you’ll be able to change to something you understand.

    It does leave out the case of a user wanting to change to a language they do not understand, but I do not care for those.



  • The same way with iOS. At some point, the third-party service have a way to link a push to a device. It does not mean that you can link an user to a device, or a specific request to a device. You get a unique ID for the notifications, yeah. And someone could tell that the app server have these ID. But that’s not particularly different with iOS. It not being exposed to the app dev directly does not mean that this info does not exist on the third-party server, that can still get asked about it.

    Unless Apple found a way to magically send a message to a specific device, from a specific external server, without anyone, anywhere, having any idea where the notification should go. Which, fair, could be done by sending every messages to everyone after encrypting it for a specific recipient, but that would be a bit inefficient at this scale. The trace for push notifications exists, whether you’re using Apple or Google as the backend.