European. Polite contrarian. Insufferable green. History graduate. I never downvote reasoned opinions and I do not engage with people who downvote mine (which may be why you got no reply). Low-effort comments with vulgarity or snark will also be ignored.

  • 3 Posts
  • 475 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle
  • Walking the streets of Cambridge without a smartphone, with nothing to do but look at blue jays and squirrels has replaced buzzing notifications in my pocket.

    There’s a middle way. Turn off the notifications. Or, go crazy (and this also foils most tracking): airplane mode.

    This article is becoming a bit of a chestnut. IMO the cold-turkey advice is only appropriate to some personality types (maybe most of them, admittedly). It also occurs to me that “right to be unknown” is basically exactly the same as “right to privacy”. Still, the author writes well and it would be great if people listened.



  • I don’t see much indicating him as a former communist

    He talked about it - some variety of Trotskyism IIRC. A bit of a surprise but shouldn’t have been. Tons of former Maoists have been in high positions. Even a neoliberal head of the European Commission (Barroso).

    On the supposed virtues of communism, you won’t convince me but I suppose you know that already. IMO the world would have done very well to listen to George Orwell, someone who saw through it all on the basis of up-front experience 90 years ago. That might have saved an awful lot of needless suffering. Or Orlando Figes, who wrote a book whose title says it all: “The USSR: A People’s Tragedy”.



  • This seems right. Personally I’m not sure I could roll my eyes harder at the fact that so many people in 2026 are so ignorant as to be prepared to call themselves “communists” - after all the famines, the purges, the 40 years in which much of Europe was struggling to escape (literally) from communism… And then I saw that you, too, call yourself a communist! So I guess I’ll stop there.

    Except to recommend you the Ones and Tooze podcast, in which the brilliant host (an ex-communist) recently did a whole series, in great and illuminating detail, on the various communist thinkers. Which I listened to… dutifully.


  • Out of interest, how do you know it’s sockpuppets?

    To be honest I’m genuinely a bit interested in who this might be. I’m imagining a disgruntled Hong Kong exile with too much time on their hands. Also seems likely to be Chinese in that they have a top-down concept of information, not seeing that obvious and relentless propaganda will just backfire with a sophisticated and relatively informed audience. Perhaps I’m being slightly optimistic, but I can’t see how they’ve convinced anyone here that “China bad” who didn’t already think that.



  • Ironically, the most active user on the current #2 China community, !china@sopuli.xyz, is an absolutely indefatigable anti-Chinese propagandist.

    This person, @Hotznplotzn@lemmy.sdf.org posts multiple times per day, usually quite sensible and well-sourced articles, but always on the same downer subjects (repression, Uighurs, corruption and so on) and never anything that paints China (let alone its government) in the slightest positive light. Since nobody else in this community can match their posting stamina, the end result is a community that, to newcomers, looks like one rando’s “I hate China” blog. Hardly surprising that it’s not a very successful community.

    I’ve asked this user to consider dropping the tempo a bit, and been met with defensiveness. I complained in private to the mod, who is completely AWOL, and they didn’t care. Oh well.



  • if they can read the messages then its not strictly speaking e2ee

    Yes, it can absolutely still be E2EE: the message is encrypted and the central server does not have the key. The issue is that the clients (i.e. the "E"s) are controlled by the same entity as the central server, and we don’t know exactly what the client (app) is doing. So the fact that it’s E2EE is somewhat moot.

    This is exhibit #1 in the case for open-source software.

    PS: you obviously get this, I’m just trying to make it clearer for anyone who doesn’t.




  • Given those figures, the numbers absolutely would have run out many years ago if every mobile contract was permanent and free of charge. The operators rent numbers from a central registry, just like with domains but with a much more finite namespace. There’s no way you still have access to a number “well over a year” after last paying anything for it. In any country. Perhaps there’s a misunderstanding.







  • Could have written this whole account verbatim. You’re not alone.

    Recently I had a related experience when checking into a small hotel:

    • I sent you a message to ask when you’d arrive
    • Sorry about that, I didn’t see it because I’m not connected 24-7
    • I thought maybe you’d had a problem
    • Well I’m here now, I had a reservation, everything worked out fine
    • It’s only polite to reply to messages
    • But I didn’t see your message because I wasn’t connected

    Etc. For many (most) people it seems it’s becoming all but unimaginable not to be connected and available to anyone who wants to contact them, round the clock. This is not healthy. The fact that a technology exists does not mean we have to adopt it.


  • This problem is reminiscent of the web-browser conundrum. Perhaps the project is, by its nature, just too ambitious to be left to a small handful of volunteers. An organization, with reputation (and maybe money) at stake, needs to take the reins.

    Currently, Flatpak still uses PulseAudio even if a host system uses PipeWire. The problem with that is that PulseAudio bundles together access to speakers and microphones—you can have access to both, or neither, but not just one. So if an application has access to play sound, it also has access to capture audio, which Wick said, with a bit of understatement, is “not great”. He would like to be able to use PipeWire, which can expose restricted access to speakers only.

    Oof. Seems that snap (to take the obvious comparison) separates these two permissions. As it should.