Show HN: Fossfox – paid opportunities for open-source devs (opens in new tab)

> either companies that have their main products as open-source, or companies that make significant contributions

These two categories seem pretty distinct, and the second is pretty nebulous. What does "significant" mean here, and how well does that translate to the odds of me working on an open source project? It's unclear why Netflix and Cloudflare are included but, say, Facebook and Microsoft aren't.

If you're going to include both, it would be nice if there were a way to distinguish and filter between these two categories. I really like the idea of being able to see all the open source jobs out there, but having Netflix at the top of the list makes me unsure how many of these companies are truly open-source-first.

I'm not sure about the other companies, but I see listings for both Netflix and OpenAI that claim to offer remote work. Aren't both companies notoriously remote-hostile? OpenAI in particular seems to have been pretty vocally anti-remote lately. It might be a good idea to allow some way for people to flag bait-and-switch remote listings.

> All jobs should be remote-friendly

Would be helpful to mention where by the way; some positions are world-wide remote, others Europe or US only.

Rule of thumb: body text should never be smaller than 16px or (preferably, though the difference is nuanced) 1em as the browser gives it at the root. (This holds for form fields too, with a more concrete technical reason: iOS will zoom in on the field on focus if its font-size is less than 16px.) 12px is pretty much the lower bound of what is ever acceptable, and only in small quantities and for specific purposes, and it’s better not to go down that small.

So true. I have no problem with using and paying for a hosted, "cloud" version of the product if a self-hosting option is available. It reassures me that I can rely on this product, while not being vendor-locked.

I've certainly seen many different licenses used in COSS projects, including different mixes of them. E.g.: for my latest project I've decided to use mainly AGPL-3.0 (a pretty strong copyleft license) with specific parts licensed under MIT.

That said, my goal wasn't to limit the usage, but to be open-source, and provide self-hosting option (the 2 fundamental advantages you can provide to your users by being open-source, IMHO), while making sure nobody just runs the product on their servers, rebrands it, and sells it to others as a service (which, while possible with other licenses, is simply unethical in my book).