Hello, I'm interested in implementing a system-wide call/number blocking feature (re: https://github.com/ubports/dialer-app/issues/18, https://github.com/ubports/telephony-service/issues/43).

I know what I would like from it:

• contacts app integration
• call blocking
• sms blocking
• ability to see history for blocked numbers
• ability to easily block a number after the call

But I'd also like to hear what the community wants so I don't miss anything, so let me know.

THIS IS NOT A TOPIC TO ASK FOR PROGRESS, NOR WILL ANY PROGRESS BE SHARED HERE.
Please stay on topic and post what you need from such a functionality. Asking for progress here is pointless - once I have time and have something you will definitely hear about it

For future readers - they are not sorry. It's just yet another attempt at gaining sympathy after going a step too far (this time after they got timed out on Telegram).

They argue in bad faith and seem to think they are always the smartest person in the room, forcing their genius ideas on everyone. And once that's rejected they go with some sob story about how they just wanted to help and are being treated unfairly.

Let's not feed the troll.

@domubpkm Yeah, I know about f-call But this feature should be integrated into the OS though, so that's what I'm going to do. SailfishOS's ofono fork will help a lot.

@keneda I've been deep in ofono recently so let's say the force is guiding me pretty well

No ETAs as usual, but things are slowly falling into place.

@dizzy Silent mode / dnd was split into a separate topic (can't find it now though, not sure what happened - if nobody beats me to it I'll probably work on that one too). This one is about blocking specific numbers from being able to call/message you

I want this to be a part of the OS, not an app. As for donations, you can always donate to UBports: https://ubports.com/donate

@emphrath said in Talk to the Non-Geek People:

[...] You don't want me to touch html code

Good thing is the docs are written in reStructuredText, no HTML involved and pretty easy to write in any text editor. Or I can convert an odf/docx file for you, if you want (and make some simple diagrams if you add photos/images/doodles/descriptions).

@kugiigi It's a pin code, security is not improved that much by not showing the length - best UX would be to offer a choice.

But if we are not saving the length then it should start with no circles - we could show some helper text like "enter PIN" and "enter PIN or use the fingerprint scanner" if that's also set up.

The circles could show up empty and fill over ~200ms to preserve the current design a bit too.

Also, @lduboeuf why 12 as the new limit?

@arubislander the HA app you linked is just a webview, not sure why people bother uploading these

@dtarrant Going back to Android first might be the easiest - should all happen in fastboot so once you boot that it should be fine.

@domubpkm I have a plan and did some research, but no concrete implementation yet - I do think I could start some tests in the near future though. I'll keep you all updated in this thread.

@t12392n said in App security (new KeepassRX app):

A local Keepass should not talk to the internet.

Where did you get the idea that it does?

@arubislander said in App security (new KeepassRX app):

If the app is confined (as this one is) you don't need to blindly trust that the package in the open store was compiled by the code that is linked, to be sure it doesn't phone home. If you know what to look for, you can download the .click package and examine the contents.

All versions of OpenStore also show the permissions list and that should be the first thing people check, can't expect non-technical users to unpack clicks before installation.

Kind of related, we should probably update the popup when you install from a local .click file to show more info and definitely show permissions.

@arubislander it can't be both confined and exempt (if it actually is we have a serious problem)

maybe the thread should be locked for new replies

For future readers - they are not sorry. It's just yet another attempt at gaining sympathy after going a step too far (this time after they got timed out on Telegram).

They argue in bad faith and seem to think they are always the smartest person in the room, forcing their genius ideas on everyone. And once that's rejected they go with some sob story about how they just wanted to help and are being treated unfairly.

Let's not feed the troll.

@arubislander the HA app you linked is just a webview, not sure why people bother uploading these

Interesting, though it needs Qt 6 afaict. Still nice, I was waiting for servo to get a bit better scores on the WPT tests before trying to run it on UT, but maybe it's worth looking into for some simpler sites.

@reeered start by restoring your device with Xiaomi's tool: https://forum.xda-developers.com/t/miflash-guide-use-xiaomi-flash-tool.4262425/

@Moem a bit too much happening at work, I didn't have the energy to do anything buuuut we did figure out that Pebbles work fine on focal, the issue is in the RockWork app and it would need a reimplementation - probably less work for me to add Pebble support to mine once it actually exists.

Other than Pebble, I definitely plan to support PineTime (with Infinitime) from the start since it seems like the second most popular one.

@mymike Btw some watches require an account to set up, so I plan on having some functionality for that anyway - might be able to pull data from a Garmin account too if they are not changing that too frequently.

Ah, I didn't see the uWatch app before, I guess it was never in OpenStore? Based on the limited number of responses it lookes like PineTime might be the second most popular one after Pebble. I also had no idea it shipped with a default OS, no info on the store page (but that makes things easier).

@mymike Which model is that? I'll probably get a Garmin once I get back to running properly Though if it syncs with WiFi a lot of the functionality might not be possible without an account and the official app. Sniffing BT is not hard, but the log file contains all Bluetooth traffic the phone participated in, and even if you filter it for the watch only, that can potentially still contain personal/confidential information (notification content, health data, etc). Not something you want to share imo.

Oh fun, PineTime uses the same IC that Bangle.js 2 uses, so the OS I'm making for that would also work on PineTime