@lisali This is not a reply to your question but a suggestion: Use atom instead of qtcreator. There is a Clickable extension and qml language support. My experience with atom has been great and I can highly recommend it.
@fla Hi! Lol, ok, I joined. There's a lot I need to learn, but I'll contribute whatever I can. 😄
I still plan to develop an app that connects to the WeChat API because my husband and I need it to communicate with his family in China. If China didn't ban Signal and other messaging apps, we would have a lot more apps to choose from.
@makeixo I used the first episodes of the qml guide on Yputube made by KDAB. Its intendet for c++ but you dont need it to learn the basics. Python + qml is a different topic though. Ubports uses pyotherside for the communication between the two. You can take a look at my app if you want to see how to do it. (its pretty basic) https://github.com/Aarontheissueguy/WaterCount
There are some other resources on this forum aswell.
With that being said If Python is your first language, I recomend that you concentrate on learning it first. GUI's are'nt really that important for many fun personal projects. You can still come back to this project one or two months down the road of learning python. Feel free to ask again if you have a question.
@thrrgilag Today Fluffy crashed and I had to login again. Afterwards the warning sign was gone.
Don't forget if you have to sign in again, that fluffy is pointing to pantalaimon
Is there a recommended way to set up E2EE between two ppl with lets say 2 devices each (and one of these is UB Fluffy + Pantalaimon)?
Because there isn't any controls available from the UB Fluffy+Pantalaimon side you'll have to start the encrypted chat using another client that supports encryption such as Element. Once you've done that it should work in UB Fluffy. Keep in mind that if you have previously encrypted messages those won't be decryptable since you can't easily import the keys from another session. But new messages should decrypt just fine.
@masterchop Normally you cannot access the Android camera via v4l devices. If they are there, they are only used internally by the camera blob drivers. You would need to access the camera via an abstraction layer, as we do with our camera services for QML/Qt applications, since it needs to be initialized, activated in the correct way.
See Documentation for how to build the click with dependencies. You can check which dependencies can be installed from Ubuntu 16.04 Xenial repos in a version that fits the requirement. Maybe you'll find also PPAs to provide them. Otherwise you need to build them yourself.
But all of this is mentioned in the documentation linked above.
@keneda Eh, I might submit it to the app store. It would certainly grab attention (not sure if that's a good thing but I'm of the "all news is good news" school).
My bigger concern is after they forked Mastodon to update the back end, the Mastodon community basically shunned their nodes and the founder, who was originally all in on FOSS previously, now seems to want to close-source everything since the experience left a bad taste in his mouth, which is a real shame, since that makes it much more like the other small players in social like Parler and MeWe. There's a lot of talent on that team though, so I can still hope.