jeremija

I hear you, I've been working on peercalls.com, a video conferencing app, for the past few years and it works on all major browsers and platforms, including Firefox.

That said, I'm bummed out that E2EE using insertable streams / SFrame transform is only currently supported in Chrome.

I've also noticed that very few devs in the WebRTC community actually test stuff in Firefox.

I just run audacious when I feel nostalgic - it has support for old Winamp v2 skins. Most of the time i just use cmus though.

I don't like that I have to use their web player to listen to music. Also if their licensing deals change, the music that used to be there can disappear. I don't like that and therefore I continue to support bands via Bandcamp, from where I can download FLAC files. Unfortunately not all bands are there and some keep focusing on streaming platforms/YouTube and it's becoming harder and harder to get the music files locally.

Thanks for reporting the bug! I thought I'd fixed this issue. Which version of MacOS/iOS/Safari are you using?

Edit: I just realized that I just hadn't pushed the latest version which contained this fix. v3.0.17 is up and running now (was v3.0.15). Please let me know if you continue to experience this or any other issue!

I've been developing peercalls.com on and off on since 2015. It's an open source peer to peer WebRTC audio/video calling service, allows the users to chat, share their desktop and send files (sending files is a little buggy at the moment, works best in Firefox).

It has gotten a lot of interest in the past month and I noticed a spike in web traffic so I'm actively working on making it more scalable. I'm planning on implementing an SFU to support calls with more than 3-4 people. Right now the peers establish a mesh network and it quickly gets expensive to send video to more users.

I've also been paying attention to the criticisms of Zoom and other WebRTC conferencing services and am hoping to implement end to end encryption for intermediate servers using Insertable Streams once the functionality is supported in most browsers.

For the past few months I've been building a platform for posting articles with tree-style comments out of the box. It is written in Golang, fully rendered server-side, has no tracking, works without JavaScript, supports GitHub Flavored Markdown, code is automatically highlighted when language is specified, has a light and a dark theme (right now only on browsers that support `prefers-color-scheme` CSS feature).

Feel free to check it out and drop a comment here!

Location: Croatia (previously Amsterdam and New York)

Remote: Yes

Willing To Relocate: No, but occasional travel is OK

Technologies: Golang, TypeScript, JavaScript, React/Redux, Python, Java, PostgreSQL, MySQL, Linux, Docker, Ansible, gRPC, TDD, unit/integration/end-to-end testing, Android

Resume / CV: rondomoon.com - I can provide more info if asked by email

Email: hello at rondomoon.com

I am a full stack developer with over a decade of experience looking for remote contracting work for my company. I mostly do web app development (PWA, SPA, MPA, SSR) and am equally happy to write frontend and/or backend code. My development flow follows the 12-factor app principles, and I like automating stuff.

If a project is uses an unfamiliar technology, I am alaways keen on grokking the code base and learning something new.

I usually have a base config file that's committed and serves as an example or for developing with local services that I (or any other dev) can run easily via docker compose. Additionally, any setting can be overridden with an appropriate environment variable.

For test/production environments I have a separate config file that is not committed to the repository.

Continuous integration tools like GitLab CI, Drone CI, and I believe Travis CI have support for application secrets so that can be used for automated deployment. Alternatively, these config files can live on the servers.

Some automation tools like Ansible have the ability to encrypt the secrets so they can be pushed to the repository, but I've never done it. Docker swarm also has support for defining secrets, and I'm sure Kubernetes does too.