HNHacker News
TopNewBestAskShowJobs

AAAAaccountAAAA

132 karma · joined December 4, 2023

submissionscomments
AAAAaccountAAAA··on US startup charging couples to 'screen embryos for IQ'
That and the fact that in many cases, the symptoms are very mild, and the problem could be reasonably seen to actually lie in the society's sometimes really far-reaching demands for homogenity. And extreme homogenity is bad for innovation.

It might very well be that a double-digit percentage of the population has a some sort of neurodevelopmental disorder[1], and the extermination of such a lot of unborn people is going to be a considerable burden for industrialized countries already struggling with low birthrates, and being totally unprecented, may lead into all kinds of unintended consequences.

1) https://dceg.cancer.gov/about/diversity-inclusion/inclusivit...

AAAAaccountAAAA··on Honeybee: Calling via XMPP
https://en.wikipedia.org/wiki/Freenode#Ownership_change_and_...

It is still kind of around, but it became a completely different kind of a network under its new ownership. Most channels went to libera.chat, but others went elsewhere.

AAAAaccountAAAA··on Update on Native Matrix Interoperability with WhatsApp
The problem is that Whatsapp does not yet need to expose group chats to other platforms. IIRC, it will change in next year, though.
AAAAaccountAAAA··on Update on Native Matrix Interoperability with WhatsApp
Could this perhaps be leveraged to make Matrix groups accessible in Whatsapp? I don't really care about 1:1 chats, SMS is usually good enough for them.
AAAAaccountAAAA··on Google takes first major step: E2EE interoperability across all messaging apps
The main problem with replacing the stock RCS app is that USIM authentication requires system privilege: https://github.com/Hirohumi/RustyRcs/issues/1

If one's RCS hub doesn't have that as a hard requirement, there shouldn't be any technical reason preventing a third-party RCS app.

AAAAaccountAAAA··on Google takes first major step: E2EE interoperability across all messaging apps
We already have a some sort of prototype.

https://github.com/Hirohumi/RustyRcs

AAAAaccountAAAA··on Discord is nuking Nintendo Switch emulator devs and their entire servers
Matrix is not better than IRC. It is in some ways much worse. While I get that IRC has not exactly aged well, Matrix' performance and reliability problems are much worse than the very rare netsplits.

IRC sucks, but it can be made more or less tolerable with things like IRCCloud or Lounge (or tmux+weehcat if you happen to prefer something like that), but AFAIK nothing can help with the poor performance and the unreliability of Matrix.

While Matrix developers have finally acknowledged the problems, they have run out of venture capital, and have hard time getting any funding to fix the protocol, clients and servers.

AAAAaccountAAAA··on The First Beta of Android 15
If one is content with remote-controlling Google's proprietary implementation, it can unofficially be done by leveraging the Web UI: https://github.com/mautrix/gmessages

That however does come with all the drawbacks of adversarial interoperability.

AAAAaccountAAAA··on The First Beta of Android 15
Never, because RCS doesn't work that way.

However, someone has created an open source prototype RCS client: https://github.com/Hirohumi

It supports only carrier-provided RCS, though. No one seems to have even attempted to connect it to Google's carrier-bypassing RCS service.

AAAAaccountAAAA··on WhatsApp Outage
Not sure if I understood it correctly, but this specification seems to discuss about SIP URI based non-mobile identities: https://www.gsma.com/futurenetworks/wp-content/uploads/2019/...
AAAAaccountAAAA··on WhatsApp Outage
RCS in its standard form is to be offered by the carriers. However, because carriers in the most parts of the world refused to offer the service, Google took over that role.

https://www.theverge.com/2019/6/17/18681573/google-rcs-chat-...

Apple has so far been quiet about how, if at all, they are going to deal with carriers that have no native RCS support. Maybe they will run their own servers and federate with Google, maybe they will use Google's servers directly, or maybe it simply won't work at all without carrier support. We have no idea yet.

Edit: IMO the most worrying option would be that Apple and Google will make a some sort of exclusive bilateral deal that will make them, and only them, to be able to offer non-carrier-based RCS support, locking out any other operating system vendors from the platform. That would probably have antitrust implications, but enforcement is often slow.

AAAAaccountAAAA··on WhatsApp Outage
RCS has enough features for most people, and it will be pre-installed. After people will realize that mobile operating systems can do modern texting without any crutches from their respective app stores, they will increasingly not bother with them, and that will make Whatsapp to gradually be less and less important in an accelerating pace.

Those who actually care about e2ee don't use Whatsapp, because it is closed source and it nags users into enabling plaintext cloud backups.

Of course, if Apple's RCS implementation won't work without carrier-provided RCS, it will be dead in arrival outside North America and China.

AAAAaccountAAAA··on U.S. sues Apple, accusing it of maintaining an iPhone monopoly
You don't really need an OS API for RCS like you need for SMS/MMS, as RCS works over IP network. If you want/need to use USIM based authentication, you need a system privilege, so that you can talk to the SIM card.

Someone has written an open source RCS prototype app, but it is only for carrier-provided RCS and I don't know if anyone has even attempted to use it with Google's servers:

https://github.com/Hirohumi/RustyRcs

AAAAaccountAAAA··on What Apple's Promise to Support RCS Means for Text Messaging
> But what’s exciting about RCS is its native support for extensions. Google has taken advantage of this ability to implement its own plan for encryption on top of RCS using a version of the Signal protocol. As of now, this only works for users who are both using Google’s default messaging app (Google Messages), and whose phone companies support RCS messaging (the big three in the U.S. all do, as do a majority around the world).

A big factual error. RCS is supported by hardly any carriers globally. That's the reason why Google managed to take over the whole RCS ecosystem, running their own servers in place of the carrier's ones. Google has also choosen to rule over RCS with an iron fist, shadow-banning users at the slightest perceived violation [1].

It does not even seem to be public knownledge whether or not Google would allow generic RCS clients on their servers, but the fact that they shadow-ban those who run their proprietary implementation on a rooted device, is not exactly promising.

I am not sure why an organization like EFF should root for RCS in its current state.

1) https://www.androidpolice.com/google-blocking-rcs-google-mes...

AAAAaccountAAAA··on WhatsApp Messaging Interoperability
Yes, and failing that, you could simply revert to plain old SMS. IMO, a better course of action would have been forcing Whatsapp to provide an alternative way to access their group chats.

Or alternatively, forcing all phones and carriers to support RCS as a condition for certification, and funding the development of a quality FOSS RCS client.

AAAAaccountAAAA··on Nightmare on Lemmy Street (A Fediverse GDPR Horror Story)
[dupe] https://news.ycombinator.com/item?id=39594412
AAAAaccountAAAA··on Google Messages RCS is blocked on rooted, custom ROM Android phones
To my understanding, to use RCS on Android, you need to:

- to be able to access Internet

- to be able to read incoming SMS messages for identification

- to implement a full RCS client stack of your own.

There is an open source RCS client library in existence: https://github.com/Hirohumi/rust-rcs-core

I am not aware of anyone having been managed to connect it to Jibe servers, though. It is completely possible that Google is somehow actively blocking third party implementations, but I don't know for sure.

AAAAaccountAAAA··on Google Messages RCS is blocked on rooted, custom ROM Android phones
RCS existed long before Google monopolized it.

https://en.wikipedia.org/wiki/Rich_Communication_Services

AAAAaccountAAAA··on Don't Use Discord for FOSS (2021)
That is not made very clear in the Play Store, though.
AAAAaccountAAAA··on Don't Use Discord for FOSS (2021)
I don't think Discord's usability is good at all. It is overengineered, cluttered, confusing and messy. However, according to what little experience I do have with it, at least it works reliably.
AAAAaccountAAAA··on Don't Use Discord for FOSS (2021)
> Speaking as project lead for Matrix, I agree that Matrix clients tend not to be as polished as Discord - we are not blind to usability problems.

User interface issues are the least of the probelms of Matrix. Much bigger obstacle to its adoption are the performance and reliability issues. While on some fronts there have been progress: joining a room does not take hours or days anymore. On the other hand, some other problems - like Matrix's tendency to drop messages - have actually gotten worse in my experience.

No matter of polishing of the UI would help Matrix enough. You still need a solid technical foundation to build on. The "Sliding Sync" thing maybe could help, but being disappointed with Matrix once and once again, I don't have high exceptations.

> However, it’s not that clearcut - for instance, Element has a full product design team (albeit focused on making sure Element works for paying government customers rather than FOSS developer communities, currently). Does https://element.io/labs/element-x look like something from people who don’t care about usability?

Users don't care how much you spend money on it, they only care about results.

> So I am not convinced that blanket statements like “FOSS alternatives have awful usability” (N times over in the same thread) are helpful. They are often grounded in groupthink or completely outdated info - “my friend Alice tried Matrix in 2019 and it sucked”, or “all my friends say Matrix sucks so I’m going to copy them”.

And other times they are grounded on recent first-hand experience.

> Meanwhile, communities like Mozilla, FOSDEM, KDE, GNOME, Nix, Debian, Ubuntu etc all seem to manage to use Matrix successfully in practice. Some even like it.

Debian seems to be mostly still in IRC: https://wiki.debian.org/IRC

Same goes for Ubuntu. It is only "in the initial testing phases" for Matrix. https://ubuntu.com/community/communications/matrix

FOSDEM is a some sort of geek social club that doesn't really do anything.

Beyond FOSDEM, only Mozilla, KDE, Gnome and Nix are actually imposing Matrix on their respective communities. However, none of these are really success stories. Mozilla's downward spiral in market share has been particularly spectacular. Desktop Linux's market share on the other hand has slowly increased, but it still clearly a niche product.

> I suspect the bigger issue here are folks who refuse to use a system which doesn’t have total parity with every feature Discord has”, or who are annoyed at having to run more than one chat app; Discord is where my friends are.

More important than feature parity is reliability.

> Alternatively, can someone actually articulate the showstopping usability issues which are being referred to here (say, when using Element Web)? Weirdly enough we would like to fix them, as fun as it is reading the “Matrix has bad usability and they can’t even see it themselves” trope.

Curious. Previously you have admitted to ignoring problems in order to spite users you don't like: https://news.ycombinator.com/item?id=38351006

While I can believe the user in question can be, umm, a somewhat difficult person, self-sabotage is hardly good for anything.

If you have changed your mind, surley you can take a look at your bug tracker in order to find bug reports that need to be worked on.

My response may come up as confrontative. I really would like Matrix to be good, but so far it has been really disappointing, and the project's reactions to criticism have been historically outright hostile. While I am pleased of the recent change for better what it comes to Matrix project's communication style, I am afraid it is too little, too late.

AAAAaccountAAAA··on European Court of Human Rights bans weakening of secure end-to-end encryption
ECHR is not an EU court, but a separate entity, having for long had many non-EU member states.
AAAAaccountAAAA··on An Empirical Study and Evaluation of Modern CAPTCHAs
Would it be possible to conceive a proof-of-work that is difficult to parallelize, making it harder for GPU computing?
AAAAaccountAAAA··on Another crackdown on Boston-area pirate radio stations
Pirates were people who attacked merchant shipping without a license. Those who had a license for that were called privateers.
← PreviousPage 4 of 4