That's why Microsoft only uses Windows as the OS for the servers on Azure
How is it not a conflict of interests?
My dude you are in a sub called "Anniversaries".
I think that this is only a UX issue. Some users don't want to see the same post posted more than once, certainly not few times in a row. On the other hand, significant discussions could develop inside each of the posts.
Cross posting should have their own view. Maybe aggregate/group posts with the same content, and allow switching between comment threads(root comment as well) inside the view.
On the feed, all the subs where it was posted could be shown underneath the main content with the other meta data.
At any rate, I do strongly believe that cross posts should be handled differently than regular ones. The platform should be aware of duplicates.
You can try this list: https://github.com/public-apis/public-apis?tab=readme-ov-file
You can even use multiple APIs in a single app if the APIs you want to use are too simple(or for any other reason).
Sorry that was a typo. I meant to write 'entities' as in api entities which are crucial to describe the structure of the requests and responses.
Restful API is an approach that is very open to interpretations and mistakes. Meaning, there's nothing that forces a given api to be restful unless the devs were able to do it correctly. Even then, most apis are not expected to be used without thorough documentation.
To practice I would suggest:
Go over the principles of RESTful and try to understand http better ( verbs, request and response structure, headers etc...
There are many free to use apis across the web. Pick any of them, read the docs and try creating a programmatic workflow with that api. It can anything - minimal ui to help uaer interact with it or some background service that talks to the api etc.
Be sure to check the ebtitiea docs as well.
Last thing, it is fairly common to see swagger(openapi) and if the api does support it, it'll make it a lot easier-for you to understand it.
Good luck:)
All I was saying it should keep your phone locked after the BT was toggled
While speaking on Bluetooth toggle, I find it very annoying that in order to toggle it, you have to unlock the phone. I.e. when phone locked, you click the button, then get prompted for unlocking, then the phone is unlocked and the Bluetooth toggled. In such case, the phone should stay locked after the prompt and only toggle the functionality
I feel you my friend...
I really think you missed my point. And if not, please explain how it can undo all the damage that causes current extinctions
I second the above comment and would also recommend learning kotlin for a while before starting using it with android since both will take time to learn and android by itself is massive.
Regardless, when seeking help online, like the other comments said, be sure to be as specific as you can about your issue and questions and attach code snippets and\or logging output where applicable