Hacker News Reader

Comment by Youden | Hacker News Reader

It's been raised but doesn't appear to be a large enough issue to be put on the roadmap: https://community.bitwarden.com/t/allow-attachments-to-be-ex...

The project is open-source, maybe send them a pull request?

View on HN

I like Bitwarden and open source, but attachments are a paid feature for them, so you'd be essentially working to add value to their paid features for free. That feels unfair to me.

I think you’d be working to add quality to your backups for free. Sure, they’d also give it to other customers, but what matters is that you have it (and henceforth do not have to maintain your own fork).

I think the point is more that you'd be giving away work for free that is only usable by people paying someone other than you.

That's a more generous way of looking at it and certainly a fair point.

Isn't this argument basically true of any major open-source project? There's always a commercial user somewhere who benefits from your work without paying for it.

A contribution to Bitwarden would benefit the paid hosting, sure, but it'd also benefit folks who are self-hosting.

Well the clients are still quite nice and you can use them with VaultWarden for free and get attachments.

> The project is open-source, maybe send them a pull request?

Just because a project is open-source doesn't mean they'll accept a pull request with your feature request in it.

Indeed. Few things are worse than spending time and effort figuring out a complex repository, making and testing changes to the code and sending in a patch only to get ignored.

Good to see open source hasn't changed in 20 years. This has been my biggest gripe. You have an idea, you present real world use cases, you submit a patch.. Only to have your idea ridiculed or ignored as you point out. THEN, a few weeks/months/years later, your same patch is accepted by someone else with a twitter blue checkmark to rave reviews.

I once asked about the possiblity of adding a feature to a project. I was told before I even created the PR that it wouldn't get accepted because there would be no need for such a feature. I looked at the project a few months later and it had that feature.

Sometimes the biggest problem to getting new contributors is the current contributors. A great example of that is when Laravel asked the community on reddit why they didn't contribute or what was the biggest hurdle. Everyone responded with the guy who was triaging the tickets. Literally, he would act like a Reddit moderator. One line responses such as "Short answer is , no."

Yeah, such a pain. A common variation: you submit a fix or feature, the maintainers then commit their own version without even talking to you.

I suggested that mainly because the original poster seemed to be saying "it's so easy, just do X", so it should be minimal effort to send a PR.

If it were to be something requiring more effort I'd suggest engaging with the project and asking if a PR would be welcome first.

I never switched to Bitwarden because I don't like how it was designed but this is clearly a huge bug even though I probably wouldn't use the feature to attach files.

>because I don't like how it was designed

can you elaborate?

I already have a file server that is synced between my devices so for me KeepassXC works better (i.e.: I don't need to setup another server just for my password manager)...

Reply on news.ycombinator.com