There are countless patches that are never merged for one reason or another, sometimes just because the maintainer doesn’t like the implementation even if it works, so they implement it themselves.

If no code was used, no credit is necessary. She did credit you for testing, which a lot of projects don’t bother crediting. So take that and continue with your life.

okay, still, she didn’t steal anything from you. She didn’t use your patch, that’s all that happened. That’s not stealing.

no, because Leah didn’t use any OP’s code. Leah simply rewrote the patch because it wasn’t working. OP is just mad because he was expecting to get it to work and be merged into the project, but Leah did it first.

Reading Leah’s comments, you’ve been credited for what you did, testing. Your patch didn’t work, she didn’t use it and wrote a solution herself.

Nothing was stolen because she didn’t use your patch.

I’m sorry, but why is this in the Linux community?

sure, Nextcloud is open source, so go and post it in the open source community or in self-hosting.

come on, setting up your own DNS is not difficult at all. For my home network, it’s running in a Raspberry Pi, but before that I ran it locally on my desktop. There’s no way I’d spend 15$ a year to resolve internal addresses.

Sure, you have to be careful with the TLD you choose, but I believe that if the ICANN were to create the .lan TLD, it would be all over the internet first.

I think needing a VPN to access the internal network is a good practice. And if you’re going to be used a VPN anyway, I don’t see why you wouldn’t use a “fake” TLD like .lan for internal stuff, after all it’s just simple DNS rules.

instead of basing your definition of AI on SciFi, base it on the one computer scientists have been using for decades.

and of course, AI is the buzzword right now and everyone is using it in their products. But that’s another story. LLMs are AI.

it’s probably some sort of Snapchat automatic alert detecting the words bomb or Taliban.

but if they have all that disabled, they probably have their ads disabled too, which means they are not making Brave any money. So they don’t care.

If we had a working alternative to Android as a whole, we would surely use it. But Linux on mobile works only in few devices and not flawlessly at all. But for the Chromium monopoly we have an actual alternative that works.

yeah, the most shady part of this is that SimpleApps’ code was available in Github. They could have just used that and upload it to the Play Store.

why did they buy it from the developer instead? because thousands of people already had these installed, so when buying it from the developer they get to push their new, ad infested versions to the unwary users had the apps installed.

This is a very dark pattern IMO.

Not even close. This has nothing to do with SimpleApps.

A crappy company bought them from the original creator and maintainer. This company is well known for buying mildly popular apps and inserting ads in them for monetisation.

People who downloaded them from F-Droid should be fine tho.

not OP, but feedly is quite privacy invasive. the content you read is very valuable data, self hosting keeps your reading interests private.

that’s just a temporal patch and does not solve the monopoly situation

How can I intercept this traffic quickly?

Assuming an Android app, this is the app that I use: https://www.f-droid.org/en/packages/com.emanuelef.remote_capture/

If you’re building a program for desktop, Wireshark works great.

in that case, you’d be better by not using Google Messages. According to the discussion I linked there seem to be a few other proprietary RCS clients in the Play Store, other than Google’s and Samsung. Not sure of this myself, but it’s worth looking into it.

If you don’t want to install Google Play services, your best bet is trying your luck with any RCS client other than Google’s. Even Samsung’s (if it even works outside of Samsung phones) has a bigger chance of working without Google Services installed.

Once you find one that works on a degoogled Android, just follow the usual recommendations: install it in a separated profile, give it as little permissions as possible, maybe a VPN if you don’t want them to get your IP (although given that your RCS provider will probably be your ISP this might prove pointless), etc.

And remember to assume that it is not private at all and they are harvesting all your metadata. The encryption is proprietary too, so there’s that.

Edit: I just remembered that encryption is probably exclusive to Google Messages. So you’re screwed, I highly doubt Google Messages will work without Google Services.

I’m guessing that in the near future when Apple launches RCS, we will have more options in Android too. So just keep up with the RCS news.

that’s very plausible, I didn’t stop to look into it further than a quick read.

Google’s implementation of RCS is proprietary and that’s what most providers use. Relevant discussion here:

https://forum.f-droid.org/t/rcs-supported-message-sms-mms-app/13423

if you’re a developer, there’s a very easy and practical way of testing this without trusting anyone’s (not even Google’s) word:

compile the most basic of flutter apps or some demo and see if the app makes any kind of request to the internet.

edit: a single web search reveals that Flutter has indeed Google telemetry enabled by default. developing your web searching skills is a good habit for developers.