zlatan_todoric

Fair arguments and criticism. That doesn't make them better at all, I think we can agree on that (and as you mentioned the Web UI situation, yeah, that makes them way worse in gran total).

I wish you all good luck, the product looks good, I hope you monetize it and I hope no big corp forks it and makes some closed source alternative (because MIT license does allow exactly that).

Sorry, maybe I sounded diminishing in my post, and I didn't want that. However, the business is still open-core, even if 99% of it is open source. That 1% can taint the project more and more in the future (and MIT obviously allows for the open-source part to go fully proprietary in the future).

1% of cyanide compared to your body weight is still lethal.

P.S. I played a bit last night and I will for sure give it a try (I'm an idealist but still pragmatic and I hope people at Keep are similar)

Kudos. I appreciate the desire to be open source and the need to monetize (and I don't have a golden solution to it, so I would probably do something similar), but I just wish that people clearly define that they are open core because there are a lot of amazing open source projects out there, and it wouldn't be fair to them to be called open source when they aren't.

It looks quite interesting, that's said, I wish people would stop calling projects open source when they aren't and most if not all projects here in Show/Launch are open core - same with Keep. You have a proprietary license in the project, with parts of the code with an open source license.

Hey, we are having fun doing it :) It is already pretty nice for testing things and show us the results. It is not going to be forced on users at all and it will share parts of the code with all the third-party CI integrations that we are working on.

For me it is not only about censorship resistance, it is also about having everything stored in git (so you loose nothing if you decide to move around) and about easy way to be a node itself (you installed Radicle? Congrats, you're a node in the network - you participate, you help, you extend. You can make a permanent node with domain name but you're already a node once you installed Radicle and started the node daemon).

It is this radical idea that everyone can easily be an equal participant in the network and that they have power over what they want and don't want. Open source nature further helps you to adapt things - don't like our web UI local-first interface? Build your own one or adapt ours to your need.

Here you go [0] - the project hasn't launched yet and there are bits and pieces to be dealt with, the current focus is a bit somewhere else. You can also build from source [1] with Rust's cargo.

[0] https://files.radicle.xyz/latest/

[1] https://app.radicle.xyz/nodes/seed.radicle.garden/rad:z3gqcJ...

We are actually working on a number of CI integrations and building our own native one, for our needs.

you can choose which nodes you follow and which nodes you block - you can even decide that you will seed particular repos and not the entire node.

(P.S. I am working at Radicle)

Radicle does store such data in git - issues, patches (PRs) etc. Also, the entire project (protocol, cli, web ui etc) is fully open source.

I am not arguing anything, I am stating my opinion.

I spent my time in Purism cleaning such false claims about laptops and I was open about where we stand with it. That said, laptops have less issues than modern phones regarding freedom part and people just need to be aware and honest about it and not say "no binary blobs" when actually you will use binary blobs for crucial capabilities of modern phone otherwise you will have a brick in your pocket.

Sure, but for me, personally, if you need proprietary things to have 2/3/4G etc is not freedom, no matter where you put it.

That said, Librem5 is still ahead compared to any Android phone regarding freedom and especially privacy part.

Pine is not overpromising things and is doing more organic growth which will sustain. That said, I can confirm that I saw Ubuntu Touch running on PinePhone.

Tbh, it was very easy to slip this one in if someone didn't pay attention as it was integrated with hosting provider at that time. I removed it inside something like month (aka when I got time from other more pressing deals).

Apparently, if you have blobs separated from main CPU you qualify (secondary processors).

Hi skrap,

what would be the best way to contact you?

I would say well deserved! I am not anymore into web design nor did I ever liked it much (I went low-level and to hardware design) but when I needed to do it I used webflow and it was delight. Easy, intuitive and really great tutorials were there.

Thanks Webflow team!

Hi, I have hard time to find the email where to apply and while browsing there seem to be many missing or broken links in your docs. I really like what I read in general around the company's culture and I see I could fit in few roles, so I am eager to apply :)

Hi, your post mentions ONSITE but yet equal salary statement feels like you can live anywhere in US? (personal note, I am not in US)

Location: Bosnia

Remote: Preferred

Willing to relocate: after some time if offer is right

Technologies: technical team manager/CTO/product manager, Debian/Linux, debs. flatpaks, git, hardware, support

Resume/CV: https://www.linkedin.com/in/zlatantodoric/ and more detailed one upon request

Email: zlatan@riseup.net zlatan@debian.org

I know the manifesto, I am among original ones proposing it.

And for things that might happen in future, I would leave them for future. Building hw takes time and proper dedication - all what I am saying is to be realistic towards current situation. The blocks are no commodities but some essential parts in today's use of smartphones. And no, things don't move that fast that you will just replace it.

If done right, things could finally go into right direction or at least have some new light on it.

While the Librem5 is step into right direction, it is far away from open hardware and will likely need even software proprietary bits - so I would recommend to stay in realistic zone and help the project in any way you can.

Those are just mockups and not the end product which might heavily change due to various things.

Debian maintains its set of patches often (quite easy to handle with quilt in debian/patches). We get upstream source from upstream of course and use our patches until they get accepted (we don't force upstream to do so) when we of course remove obsolete ones.

Debian gets sponsored by various ways but the money isn't used directly for developers nor their time. It is volunteer based project and money is usually used for hardware, sprints, conferences, outreachy etc.

That said Debian does take it seriously when it comes to privacy and security so you can always report bugs on such. Do note that Debian's Chromium builds have always disabled the infamous "mic always on" option which Chromium has (or had, didn't check) by default.

Btw, Debian now moved to gitlab hosting (their own instance salsa.debian.org) so it should be much easier to contribute to Debian now. :)

P.S. while Debian Developer myself, I stay away a lot from browser and especially Chromium, and I always suggest Firefox (it has really got better last year or so).

At my company we used Jitsi (and also tried with hosting our own instance) and Appear.in. Both worked kinda fine and appear.in has limit to number of people unless you go to pay option - with more people quality would simply drop and we do have 20+ people in company meeting.

We decided to try old school - we hosted our own Mumble and while maybe not nice UI/UX, it works perfectly for 20+ people. Also I recommend as well having good headphones (with integrated mic) to avoid potential echo (jitsi echo can be annoying without headphones).

^ this! And only this.

It is defense budget for crying out loud, not "lets attack every country our rich gods don't like because it doesn't accept their dark business".

Sorry, but obviously not even Microsoft with its stash of money can't guarantee something will be success story, so we can't either.

We are perfectly capable to make this device, we can't guarantee it will be something millions will end up buying.

And the ecosystem is important for easy of creation or porting stuff (not just code-wise, but how you approach to such things) and also as I mentioned here - we also plan to work on utilizing Android support via anbox or shashlik which could potentially remove that gap (also people need to realize that Google is developing only handful of apps, those millions come from third-party devs).

On the phone we plan to produce, you will be able to install Android as matter of fact - it is just that we will not do it by our default as we want a pure Linux stack that is going to roll in updates normally as desktop is and not being attached to older kernels and heavy forks of ecosystem. Even for scale of Google it is not feasible to do it that way so they are now doing their own research and development (Fuchsia OS or something like that).

We plan to utilize things like anbox and/or shashlik so you would end up having Android apps if needed, but we will also focus on having great experience out of the box, with preset default apps.