4kimov

> Every time a maintainer finds a way to get paid, it’s a win.

Amen. It's becoming more common, and there's lots to celebrate [0]

[0] https://fossfox.com/

I see. Thanks for the input.

Good points. Those pages also contain links to old implementations (Hashids), because a lot of projects still use those and want to be able to find them.

[shard_number, primary_id_number, timestamp]

Having moved from React to Svelte, it was always a breath of fresh air to write less and have it just work. Feels strange seeing state/props/effect again, almost like I'm back to React.

Besides all the already mentioned, solid responses about looking for new opportunities (personal network, consistent daily applications, etc), it's worth noting this one too:

Become a regular contributor to specific open-source projects (esp if it's a growing and/or funded startup).

This approach might work better for those that are already comfortable w/ OSS and don't yet have connections. When applying to that company a bit later, obviously mention all the merged PRs.

For example, here's Posthog [0] showing you what you could help with thru a job post. You can find more companies like this one at Fossfox [1], shameless plug: I maintain that index rn.

[0] https://posthog.com/careers/full-stack-engineer-growth#typic...

[1] https://fossfox.com/

Thank you. Yes you're right, location/remote has to be adjusted for better experience. And I'll see what I can do regarding the email '+', thanks for the heads up.

Oh I like that. It would include people that enjoy working at open-source companies, but their role might not be directly foss-related on the daily (eg: devops, website, etc). Thank you for pointing that out.

Good point. The code used to have a "work directly on open-source" checkbox per job, but it's hidden for now because I wasn't sure about the edge cases: people can be asked to switch projects later, some companies have their main product as open-source but the position is not directly related (eg: devops), etc. Perhaps I should bring it back and see how it does. Thank you for the feedback.

Indeed. Some companies limit to countries, some to timezones (+/- a few hours), some to regions like you mentioned, and others might have a language requirement. I've been trying to figure out how to surface that properly without making it too complicating for either the poster or the viewer, and I'm honestly not sure yet.

Reporting/flagging features are def on the todo list & not yet there. I agree, they'd be great to have for better moderation. All good points.

Yeah, I might've gotten used to it by now - need to experiment a bit & adjust. Thank you for the feedback.

Great questions, atm the index contains either companies that have their main products as open-source, or companies that make significant contributions (eg: Netflix, Cloudflare, OpenAI have thousands of Github stars).

All jobs should be remote-friendly. There's nothing to do - if you see the jobs, they should be relevant to you.

Some companies do have physical offices (meaning you're welcome to work from there), and those cities are listed if you click on the company's name. Right now it's region-biased per country -- if you scroll to the bottom and click "more" you can change the country. There's def still work to do (visas, non-remote, fine-tuning, etc).

Nice, thanks for adding to resources.

Thank you.

Thank you. I agree: it's a great moat against closed-source competitors. Plus I'm noticing more and more businesses going with permissive Apache 2.0 licenses (or similar), which is great for the public as well.

I'd say it's also important to remember the types of projects that are easier to monetize. About a decade ago I wrote an OSS library that gained some nice traction, and it wasn't really monetizable (granted I didn't want that anyway).

Then there's companies that write open-source software and are not only successful in charging for it, but also have funding. I run Fossfox [0] that indexes companies that have either open-sourced their main products (eg ClickHouse) or that heavily contribute to open-source (eg OpenAI). The ones that open-source their main products: some of them do use copyleft licenses, but most surprisingly go with Apache 2.0 (and of course use some dual licenses; with "ee/" directories). The one thing a lot of them have in common is providing hosted versions of their software. A lot of customers don't want the hassle of running it themselves, and do pay for hosting and support.

[0] https://fossfox.com/

Open-source blockchain analytics tool [1]. Lots of use-cases, but a straightforward one is compliance. Many alternatives in the space, but most are SaaS-only.

Still early in the journey, but feel free to star or follow along:

[1] https://github.com/barreleye/barreleye

That's right, moving sats via LN is done off-chain. Once the channel closes, that's when it settles to L1, at which point tools like Rotki can help you figure it out.

Anyone interested in Lightning should also check out Taro protocol, which was announced recently by Lightning Labs.

Possibility of stablecoins on Bitcoin via the Lightning Network.

Thanks for the feedback. Heard that argument from a friend as well. Do you associate Polyzag with anything, or is it relatively neutral sounding?