HN user
Android should really use a modern kernel. All the forking mess involved in Android updates is a terrible problem predicated by the lack of generic drivers on mobile devices.
Copperhead[0] has been working to apply security patches to the kernel for some time and PostMarketOS[1] has an eventual goal of using the mainline upstream kernel. Really pulling for PMOS.
I have doubts, but I've been waiting for a phone like this for a long time. I hope it works out and gets enough funding. I'm glad they didn't make compromises on the OS, hardware switches, etc. I wish more companies would cater to passionate yet non-mainstream markets. It's crazy a truly hackable linux phone doesn't exist today.
I support the whole idea, but I think it's premature.
The Riot app in my experience has a pretty unwelcoming UI/UX experience and is still insanely buggy. Things like Jitsi integration, widgets and a phone partnership should be after a solid, stable 1.0 MVP IMHO. Encryption is still opt-in and beta.
So super supportive of the environment, the momentum and a native matrix phone partnership is the right move eventually, but please get it stable, fast and polished first before branching out too far.
You really should not upload other people's complete works while under copyright.
Edit: Nice License
Copyright (c) 2017 Zack Thoutt
That's a shame. I really like the React interface, but would never build a company with it at the core just on the principle. Revoking on first strike is super defensive and just plain slimy.
If there were something like create-preact-app (not forked from create-react-app) I'd be all about it. With special decorators, dogmatic separation of templates, styles and logic, and mutability I don't think I can get aboard the Vue.js train though I'll admit I haven't dove deep yet.
The worst part is how Facebook seems to be asking other big players to follow their lead in adding kill switches to FOSS. It'd be one thing if it were just React. Devs shouldn't let this become common practice.
- Get an app to block them
I'd soon change my number before resorting to most apps. Unless it's like uBlockOrigin where I just feed blacklists into it, I'm not really okay with giving an organization besides my service provider my call history. Read Nomorobo's TOS sometime, it's a doozy.
I don't want to stream, which puts me in the minority. I want services similar to GOG.com or Steam. I want to buy something digitally, have it stored remotely, but allow me to pull it down locally and have it so I can take it elsewhere if I want. That way old, unpopular or niche media can exist on the platform forever and I get my content on my devices when I want it. No fancy monthly subscription with a subset of content, I'll buy each piece of content and pay full price for it.
I realize this is not the 'vision' Hollywood has for their media and most people just want to stream content and not own it anyway, but all of this is very anti-consumer.
If you have Google Play Services installed, it will try to use it. If you don't, you can install the apk from here https://signal.org/android/apk/ which should auto update. Their permissions list is still kind of whack and everyone else on android except you is going to have Google in between every message so...
Cheers. Yeah for sure, I was too lazy to make a PR on nixpkgs, but this[0] is what I wrote if anyone stumbles on this using NixOS. The nix package manager can be installed on top of most OS's too.
Syncthing has a mobile app and there's an app for pass called PasswordStore[0] using OpenKeychain[1] (pgp manager). I'm not a fan of putting my private key on my mobile, but if I were, this would be a nice setup.
[0] https://github.com/zeapo/Android-Password-Store
[1] https://github.com/open-keychain/open-keychain
Edit: yeah for ctmg support, probably have to hold out for something like PostMarketOS to save us.
I use pass and love it. It provides a lot of flexibility. To fix the "website metadata is leaked in filenames" issue, I use another project by Jason, ctmg[0]. I changed the pass directory to be one directory deeper, encrypted it and just do `ctmg open` when I boot to open my password list (similar to unlocking a keypassX store) then use pass as normal. On shutdown, the opened folder is re-encrypted automatically. You could also set a ctmg close on a timer if you don't want the list to be available during your entire session after open.
Other things I do:
* store all the files as .toml files so I can rip specific keys with a custom script.
* Have a directory for web so `pass web` will give me all websites. Have a script to fill username pass for each.
* Have a directory for contacts. Then wrote a script to generate vCard files by crawling and pulling keys, base64 profile images and all.
* use syncthing to keep all devices up to date.
It's pretty slick workflow IMHO