@ukphil from what I know, each app on UT has to send the metrics to the lock screen. So, the lock screen doesn't collect message counts across devices. i.e. When you press send on the device, it probably says to update the count somewhere in the Telegram-app code, rather than the data being pulled from the telegram server, which I'm not sure even counts your messages.

Can you tell use a little bit from the ubucon europe? What feedback did you get there?

@prog-amateur Moto G 2014 added, indeed not affected with its Quad core Cortex A7

@matridium Have just looked out receipt which states 2450mAh battery

@advocatux Yeah, that would be neat. I'm trying to get something cool in the pipeline for next week, though, so stay tuned!

@libremax need to saturate youtube etc ,with howto vids n such,to get into the publics eye

"Ubuntu Touch is Alive and Strong" @libremax

@markalexa In the proposed configuration, using the phone with one hand would be less comfortable, I believe.

Intro to the simple API for a chat interface: https://deltachat.github.io/api/

@revoltevidente It would be nice to have Libertine working on the N5.

@advocatux said in Community infrastructure: Forum and Telegram: @guru said in Community infrastructure: Forum and Telegram: +1 for using the (existing) mailing-list as primary channel for technical discussions and support. Are you talking about the UBports's ones or the old Canonical's Ubuntu-Phone list? Both would do the job. The old one even better because a lot of UT users are still subscribed there and would may be encouraged to move to the UBports devices.

Thanks @PhoenixLandPirat Can you give a clue as to which phone may support this so i can start looking for it. I am sure I saw instructions a while back for Anbox on some UBports devices, but it didnt work with nexus 4 which I had then so didnt look further - by support i mean something that sort of works, not finished and amazing Lets hope whoever was experimenting with swype chimes in and I can have a play

@hummlbach follow this link and all will be revealed. Well mostly and there's a wallpaper https://t.me/ubports_news/72

@leclem : Hello Did you collect some information about this subject ? What's you feeling ? Regards Pulsar33

Awesome! I think we need more initiatives like that.

@flohack Source was from https://www.techarp.com/guides/complete-meltdown-spectre-cpu-list/4/ I have concluded that only MX4 and Nexus 4 are affected. However, I didn't know that the MX4 was affected and probably the Nexus 4. It means, almost all core smartphones compatible with UBports are affected by Meltdown/Spectre (it is a big concern). I hope another A53 smartphone will be in the core list in the future, despite the fact that I know it is far from easy to port UBports on new devices. By the way, it seems that Snapdragon 400 is made with 4x ARM Cortex-A7. Could somebody confirm it ? Because, it would mean that Moto G 2014 can be not affected. Thank you. Source : https://www.gsmarena.com/motorola_moto_g_2014-review-1139p5.php

@hummlbach said in We're delaying Ubuntu Touch Q&A 26: I'm also enjoying the biweekly shows very much and wanted to keep it as it is. But yes, as you said, the devs should decide what is most appropriateis for them. Yep, that's pretty much what I'm trying to get across. The schedule should be up to the devs and how they can best use their time. But I'll just add that sometimes less is more. For example, if the devs are asked and answer the same repeated questions (over and over and over) in the Q&A sessions, many will stop watching. That is, in some cases, too much frequency can drive away community engagement. Similarly, scheduling a Q&A, and then canceling it on short notice (for whatever reason), doesn't promote future watching. Of course, if the devs have a big announcement to make, and want to announce it live, no need to wait for a Q&A. Just schedule a special live announcement, and I'll tune in!