I always wanted to contribute to OSM but found it a bit daunting.

Any contribution helps! Hell, I went around town just looking for bike parking racks to add, and was able to put dozens of new ones on the map. You can even just label house numbers (with the aforementioned apps listed in the comment you replied to).

I mean, true…but I don’t think the average user is paying for the service rather than they’re paying for not having to worry about setting up everything needed to get syncthing working.

I don’t consider myself a luddite in any way, but within five seconds of reading syncthing’s install instructions even I basically just said, “yeah…no.” And I say that AS a nearly 12 year semi-advanced linux user. It’s not that it’s difficult. But difficult enough to not be worth it for the average person.

Too bad for Apple users though

For images I highly recommend Immich. It’s the Google Photos equivalent, and it works excellently.

I use SyncThing for documents, but photos from my phone go to Immich.

this was my experience too. kept putting it off because I assumed I’d need to tinker a bit. didn’t at all, worked immediately with only the simplest configuration. genuinely amazing, I wish my software worked that well.

Haven’t used this feature before, but this flag might be what you need

You know Dropbox? Google drive? OneDrive? That’s file synchronisation. Files across multiple devices kept in sync by the software provider. Except in the named cases above, all your data is uploaded to their servers. With syncthing there’s no cloud server, just your devices operating over the internet. So you have some backup responsibility to cover.

Caveat: I’ve never used syncthing and I wrote the above with a total of 10 seconds of reading their website and so it is entirely possible I’m completely wrong about everything and so I emplore you to do your research.

Yes. It may be a bit silly but I’m pretty happy / proud that I’ve had some contact with him while working on it :D

I get the thought, but your phone can also have a security breach at any moment, ESPECIALLY because normal user error is by far the weakest and most often exploited attack vector.

Bitwarden’s vaults are also encrypted with the option for even stronger argon2id encryption. Bitwarden themselves can’t access them or reset them. It is open source and most importantly, audited. KeypassXC has only had one audit ever. (Though that passed and I would also definitely recommend keypassXC, it is great software security-wise)

The database is stored, encrypted, once on their server and once to each device you sync to, so it is available locally.

Even if they had a security breach, by design the assailant couldn’t access your database any more than they could access your keypass database.

You can also self-host it which would bring it exactly to the level of keypassX variants as far as attack surface.

Not to mention with bitwarden, you will also only need one key. That is the whole point of a password manager.

“It is available locally and a lot better…” is simply untrue. They are both great options. Just whatever works best for the person. Bitwarden has a ton more QoL options and enterprise options, plus separate, shared password databases and such for families and companies. Again, just as secure.

I have a lot of experience with both. As a tech savvy user, I slightly prefer KeePass. Syncing between devices is slightly more painful, but I find it to be more reliable, and it doesn’t have the attack surface that Bitwarden does. (While encrypted, Bitwarden still really wants a web server and a local database connection.)

VaultWarden is probably better for those who can’t be bothered to move a file around and want direct browser integration. With KeePass when you need a password, you’ll make sure the username has focus and then alt+tab to KeePass and hit “autofill”. Some sites won’t take “username{tab}password{enter}” and you’ll have to customize the configuration.

VaultWarden is better at prompting you to add new passwords. I prefer the workflow that’s encouraged by KeePass, where you open the app first and use the app to open the URL. (You can do this in VaultWarden too, but it’s less obvious.)

While I personally use KeepassXC and Keepass2Android on mobile devices (as with KeepassDX there is no reliable way of syncing the database that I know of) to other less tech-inclined people I’d always recommend Bitwarden as it is much more suitable to most people’s usecases.

What’s not simple about it, as a password manager? Pop in the name/uri, pop in a username, pop in/generate a password Bingo bango Is there a level of complexity I’m missing, or alternatively is there a simpler approach?

It uses the magnetic field sensor on the phone (compass). It can only detect magnetically active metals and also kinda weakly, but it’s quite fun!

It works pretty well! I found in my one quick test that a pair of known points on a diagonal offer the best tracking. Definitely need to play with that feature again.

Everything runs locally, OCR, ML, etc, which can be a bit taxing on lower end hardware, but there are ways to disable the more advanced and computationally expensive features, like NLTK for advanced Natural Language processing.

Your data is stored locally on your server and is never transmitted or shared in any way.

https://docs.paperless-ngx.com/

There seems to be a huge overlap in functionality. But a major difference is that Paperwork is a local application that runs on Windows and Linux, while Paperless has a web front end that makes it accessible anywhere (it also has some independently native apps for mobile).

Attempts to remove datamining, disallowed from installing microsoft proprietary extensions.

It removes the proprietary part inserted when MS builds the code. This unfortunately makes other proprietary extensions useless, such as Dev Containers. You can still use the main extension marketplace by changing a .json but some MS extensions won’t work at all (tried it last week).

I’m in the exact same boat. If someone figures out how to get tap-to-pay working on graphene, I’ll be daily driving it so fast.

Sad face. What phone do you have?

LineageOS is very stable and usable as a daily driver, meanwhile PMOS struggles to deliver basic functionalities like calling and sending SMS.

LineageOS has a bigger community and supports more mainstream devices, where PMOS primarily focus on PINE64 and Purism.

Lineage and Graphene are based on android and bear the danger of support loss when google drops support.

PostmarketOS is actual Linux (alpine is the base to be exact).

Graphene definitely is a lot more advanced since it uses all the proprietary blobs of android. There is no use in comparing the two. Its like comparing lemmy and reddit in terms of technical finesse.

It works very well for some apps already but it is highly dependent on people supporting either financially or through contributions (code, issues, translations, documentation, tutorials).

Technically, every smartphone is a computer. Sorry if you thought you bought a phone. :)

The difference is that this is a full fledged linux operating system instead of the proprietary crap that comes with ios and android.

The downside at this point is that it’s not in end user stadium but a lot of folks are working on making that a reality. If you consider yourself a tinkerer, chances are you might be able to test it, maybe on a non daily driver phone if you have an old one, especially if its out of support.

With a de like kde mobile, it can be closer to a phone experience. Proprietary, obscure and unmaintained drivers for several phone components make such a project harder to develop.

It can be installed on several phones… Probably not yours though.

Not any phone to be totally honest but many and growing.

Check here to see the devices that are supported.

But disclaimer: its a foss project so it wont ever be perfect and if you like the project, consider contributing and help solving issues instead of judging because that doesnt help anyone.

deleted by creator