https://community.signalusers.org/
From the official site, the link is at the bottom : https://signal.org/
https://community.signalusers.org/
From the official site, the link is at the bottom : https://signal.org/
Did they stop maintaining it in general or just publishing on Accrescent?
On Accrescent, after 7.0 : https://github.com/you-apps/ConnectYou/releases/tag/v7.0
They're now on 9.0 : https://github.com/you-apps/ConnectYou/releases/tag/v9.0
Don't know when that has ever happened.
"Contact you" left accrescent after they stopped updating on it.
They'd also changed the app's signature, so updates wouldn't have worked.
There's no magic solution here.
It's up to developers to assume their responsibilities and not leave users without any information. The trust we give them is not limited to the app's code.
Says who?
GrapheneOS founder says it :
TOTP has horrible UX and I'm barely willing to keep using it for sites without FIDO2. Too weak and can be phished anyway. TOTP doesn't add any significant value on top of using a password manager with random passwords. FIDO2 adds lots of value and can entirely replace passwords.
TOTP really needs to die especially now that there are passkeys (multi-device FIDO credentials). Most people shouldn't ever have to learn that the horrible TOTP approach even exists. It's not good that it exists since sites are spending their time adding that instead of FIDO...
Mod note: removed link to Twitter account with protected posts. Most forum users won't be able to read the quoted tweets since they're not following the account.
Waste of time, TOTP doesn't add anything for security if you have unique password for every apps/websites.
It should no longer be deployed today.
hey can use my donation to improve security?
Security isn't bad because of a lack of resources, it's mainly an ideological issue.
They consider that what is generally defined as good security practice only applies to closed-source proprietary, and that open-source services don't need it.
There's a complete disinterest about security.
I believe that most apps don't use this option.
It's an Android option, so if the apps aren't compatible, it won't work. This is not a GrapheneOS problem.
Can you give examples of security and privacy features?
You can check here about each android's version : https://developer.android.com/tools/releases/platforms
For android 15 : https://developer.android.com/about/versions/15/features?hl=en#privacy
When you go to an application's settings, at the very bottom, you'll see “target sdk” and “mindsk”.
Minsdk indicates the oldest supported Android versions: https://apilevels.com/
The targetsdk should be set to 33,34 or 35 (33 will soon be obsolete).
If you have applications that are (far) below these values, consider installing an alternative, more up-to-date app.
Sorry but I still don't understand the problem
Termux targets the latest improvements from android 9.
To get automatic updates, an app needs to target at least android 12, and we're coming soon to android 15. Termux doesn't benefit from the latest security and privacy enhancements. It's very old, it shouldn't be installed.
Isn't that an app that belongs on every cell phone?
For what purpose exactly?
Yes, registrations are currently limited (just need to ask, it's not really close), but the question (as I understand it) was : to add an application, should I contact the developer or accrescent?
It's up to the app developer to do it. Accrescent will only give permission to publish apps, they don't publish apps themselves.
https://youtu.be/WkQ_OCzuLNg?si=K8JSRN6KO-McHu2i&t=1301
Start from 21:41, they talk about it.
It makes sense, but it's highly unlikely to have hardware security equivalent to a current pixel on a TV.
They will : https://x.com/GrapheneOS/status/1795161400580469158
Once the desktop mode and hardware virtualization are more mature, GrapheneOS will be quite usable as a desktop OS using DisplayPort alt mode, USB mouse/keyboard, etc. from a phone/tablet. No reason we couldn't support a laptop if there was one meeting the requirements.
But as qp5235 has indicated, it's unlikely that desktop mode will be fully functional for Android 15, at least at the official release. We'll see in few weeks...
Can't wait to see the desktop mode improvements.
A first step towards a GrapheneOS PC 😎
You can already use dark mode with chrome://flags , but it's not always well optimized.
Search dark mode and enable it.
If I'm not mistaken, GrapheneOS has reviewed its guide before it was released, but has indicated that they don't agree with everything. I often see his posts on twitter.
Anyway, it's always best to refer to the official website and social networks for the right info.
There's a lot of misinterpretation out there about GrapheneOS work.
https://grapheneos.org/faq#roadmap
What is the roadmap for GrapheneOS?
To get an idea of the near term roadmap, check out the issue trackers. The vast majority of the issues filed in the trackers are planned enhancements, with care taken to make sure all of the issues open in the tracker are concrete and actionable.In the long term, GrapheneOS aims to move beyond a hardened fork of the Android Open Source Project. Achieving the goals requires moving away from relying on the Linux kernel as the core of the OS and foundation of the security model. It needs to move towards a microkernel-based model with a Linux compatibility layer, with many stepping stones leading towards that goal including adopting virtualization-based isolation.
The initial phase for the long-term roadmap of moving away from the current foundation will be to deploy and integrate a hypervisor like Xen to leverage it for reinforcing existing security boundaries. Linux would be running inside the virtual machines at this point, inside and outside of the sandboxes being reinforced. In the longer term, Linux inside the sandboxes can be replaced with a compatibility layer like gVisor, which would need to be ported to arm64 and given a new backend alongside the existing KVM backend. Over the longer term, i.e. many years from now, Linux can fade away completely and so can the usage of virtualization. The anticipation is that many other projects are going to be interested in this kind of migration, so it's not going to be solely a GrapheneOS project, as demonstrated by the current existence of the gVisor project and various other projects working on virtualization deployments for mobile. Having a hypervisor with verified boot still intact will also provide a way to achieve some of the goals based on extensions to Trusted Execution Environment (TEE) functionality even without having GrapheneOS hardware.
Hardware and firmware security are core parts of the project, but it's currently limited to research and submitting suggestions and bug reports upstream. In the long term, the project will need to move into the hardware space.
The information is good: GrapheneOS wants to leave Linux in the long term.