DKIM makes it much more difficult to spoof email addresses, assuming your email client actually supports them.
Checking various emails I've received from @google.com addresses, they have DKIM set up and gmail is validating using it.
DKIM makes it much more difficult to spoof email addresses, assuming your email client actually supports them.
Checking various emails I've received from @google.com addresses, they have DKIM set up and gmail is validating using it.
You're mostly right. Newer devices won't share their entire app list by default, at compile time you need to enumerate every app you want to query for, or add what are essentially a list of intent filters (which are like "I want to talk to apps that take this kind of message and payload"). There is still a permission that lets you list all apps like you were able to on pre API 30 devices, but Google makes it pretty difficult to get onto the app store in that state.
You can still send intents as much as you like though (as long as you know the recipient), since they're the basis for all inter-process communication.
My point is more that an app developer can't and doesn't need to use the play store to get the list of apps you have on your phone. This requirement to have the play store almost certainly isn't malicious and I disagree with the notion that apps shouldn't be able to use what is essentially system infrastructure to improve their apps. That said, given this is an app targeting the fediverse, it would have been nice for the developer to have made a universal APK build that didn't require the Play Store.
If this error message is actually talking about Google Play, not Google Play Services, I would bet that it is because it employs Dynamic Feature Modules; something which can only be delivered over the Play Store infrastructure. They're pretty common in modern Android development since they can substantially improve the user experience for users with Google Play enabled (which is most of them).
Also, I am aware this is being pedantic, but Android just straight up already has an API to get every installed app on your device and interact with it, even on a de-googled phone.
Social media is not a good replacement for real life community (look through my comment history and you'll see me expressing exactly that repeatedly), but we can't be oblivious to the fact that for many children their only connection to fellow queer people may be online. If you live in a small town or community where there are no other openly queer people, or if your school, peers, and parents are hostile to queer people you won't have much choice in where you find community.
Are you Australian? That just feels like kind of a US centric lens to analyze this through, though you're right that loss of community is a byproduct.
Like, I'm not exactly happy with the Albanese government, but I would say that most negative LGBTQ things they have said or done have been cowardly attempts to avoid drama from the Liberals, not active bigotry
From a quick Google, it seems like Mullenweg is a complete jackass
Mozilla's next largest source of revenue is subscriptions and advertising (source 2021 financial report), by a wide margin. That "useless shit" is their other revenue, and they're investing in it because they know they need to diversify revenue to fund Firefox. You're suggesting they kill it because it's not their core (unprofitable) business?
Making a breaking change to the mobile API also breaks old outdated installations of the app. Websites and their APIs are usually synced, apps not so.
If they were really motivated to stop your method, they could just obfuscate the frontend with webpack and break your scraper every time they make an update.
I suspect that any of the methods proposed here would be prone to a C&D, but IMO the safest legally would probably be the RSS method (not a lawyer though). Reddit's RSS feeds are public, documented, and available without the need for private APIs, authentication, or an API key, so I don't see how they could claim that a wrapper is unauthorised/illegal. Documenting their private API however seems like a gray area. Google LLC v. Oracle America, Inc. found that APIs are copyrightable, but this use may constitute fair use.
Is there a reason you're scraping data rather than attaching a network sniffer/reverse engineering the official apps and documenting the results? Or map the RSS feed to an API? The main thrust behind my comment is that I think scraping is pretty fragile, so I'm interested as to why other options are infeasible.
Do you have a data feed to pull from, or some kind of list of matches? It shouldn't be too hard to use a simple python script to parse a file and post automatically on a schedule. I maintain a repo that doesn't exactly match your use case, but I could maybe add your functionality depending on complexity
Verizon sold Tumblr to WordPress in 2019