• 42 Posts
  • 301 Comments
Joined 3 months ago
cake
Cake day: April 2nd, 2025

help-circle


  • Under the new system, monitoring of a person’s messaging must be approved by a three-judge panel and should only apply to a limited number of cases. Interior Minister Gerhard Karner told the news conference it was only expected to be used on 25-30 people a year.

    If it is more than 30, a report must be sent to a parliamentary committee, the government said, addressing concerns about mass surveillance and the infringement of people’s privacy.

    “The police must have a well-founded suspicion of a possible terror attack” to monitor a person’s messaging under the new system, a government statement said.

    Once parliament passes the legislation, a tender process for monitoring technology would be launched, and monitoring would begin in 2027, the government said.




  • I found this in US Code Title 15 Subtitle B Chapter VII Subchapter E Part 791 Subpart A § 791.4:

    § 791.4 Determination of foreign adversaries.

    (a) The Secretary has determined that the following foreign governments or foreign non-government persons have engaged in a long-term pattern or serious instances of conduct significantly adverse to the national security of the United States or security and safety of United States persons and, therefore, constitute foreign adversaries solely for the purposes of the Executive Order, this rule, and any subsequent rule:

    (1) The People’s Republic of China, including the Hong Kong Special Administrative Region and the Macau Special Administrative Region (China);

    It looks like the determination of this “long-term pattern” was put on the books no later than 2024. Since Title 15 is about Commerce and Foreign Trade, it seems reasonable to think that hostilities being considered by the US are not just physical hostility, but also economic hostility.

    I imagine there’s also political hostility to consider. I haven’t been following election interference news, but wikipedia has an article about it, so I suppose it’s at least a concern these days.






  • It was more than a few years ago when I switched my desktop systems from Windows XP to Linux. I was already familiar with the new environment (having already used various unixes for years) so the transition was mostly a matter of replacing my favorite apps and wrangling Wine into running my games. Both those tasks are pretty easy these days.

    More importantly, Microsoft’s adware, spyware, and hardware demands at that time were nothing compared to now. If I were to make the switch today, I imagine it would be not just a breath of fresh air, but more like being instantly cured of debilitating asthma. What a relief.

    To people planning to switch with no prior experience: Please be patient. Like moving to a foreign country with different language and culture, it will be awkward and possibly frustrating at first. You will master it over time, though, and end up with control of your computer and data again. Well worth the investment, IMHO.



  • Well, your critical comment failed to recognize that I was contrasting the core protocol against an implementation augmented by XEPs, and what the latter would mean in practical terms. It overlooked most of what I had written, which could most simply be explained if you had only seen/considered a fraction of what I wrote. No patronizing intended.

    If hurried reading was not the cause, then I don’t want to speculate on what was. Instead, I invite you to read it again later, and consider interpretations that you hadn’t at first.

    Or just ignore it. Good day.



  • Neat idea.

    One of the problems caused by certain litigious corporations is that a lot of community-developed knowledge about game/emulator compatibility is lost when an emulator project is forcibly shut down. A separate repository for that knowledge, like this one, could help preserve the information.

    I’m disappointed that it doesn’t show game details unless the browser allows off-site images, and doesn’t show any information at all unless the browser allows javascript. This requires users to expose themselves to security and privacy risks in order to use the site. I would consider contributing if they fix this.







  • Is [XMPP’s lack of popularity] really just a marketing/UX/UI problem?

    No, there is more to it than that. Off the top of my head, these issues stand out as major hurdles:

    • XMPP is a relatively basic protocol. By itself, it cannot compete because it lacks modern features like end-to-end encryption, persistent message history, group chat, etc. It does have extension specs (XEPs) to provide many such features, but it still lacks a single cohesive spec identifying and unifying the important ones. You could call it fragmentation. This makes it overly complex for implementors, and leads to the next problem:
    • Someone wanting a messaging service with a competitive feature set must first identify at least one server that implements all the relevant XEPs, and a client for each of their devices that implements the same. That’s not viable for most people, many of whom have only a vague notion of what a communications protocol is.
    • Ever since public XMPP support was dropped by big services like Google and Facebook, the availability of reliable, free, public servers has all but vanished. Most people wouldn’t know with confidence how to find one, let alone one with all the needed extensions. And even if they do find one, most will be unable to assess whether it will still be running in ten years or more. This makes it quite a gamble to tie your online identity and network of contacts to whatever server you find.

    So, while XMPP (with appropriate extensions) is still a capable protocol, the expertise and support required to make it competitive is not readily available to most people. I might suggest it to small groups who have local expertise to get it all set up and keep things running well, but not to the general public.

    Meanwhile, Matrix has a unified spec with a rich feature set, a variety of homeservers and client apps that support it, sufficient momentum for continued development, and the critical mass to make it viable for global public use.