l3db3tt3r @ l3db3tt3r @piefed.social

Posts

0

Comments

18

Joined

1 mo. ago

Maybe start here? https://fightchatcontrol.eu/

It isn't criticism if it isn't based on fact. The U in FUD stands for Uncertainty; and what do you think "might" falls under, or it's relation to sowing Doubt?

The law related to job postings, is a labor law, that also covers minimum wage, and uses the same definitions. Labor Code Section 432.3 (Pay Transparency Law) Labor Code Section 1197.5 - California Equal Pay Act (Fair Pay Act) Labor Code Section 2750.3 (Employee vs Independent Contractor Classification)

Let me do the work for you; since you'd rather just spread FUD then look for facts.

1. https://www.linkedin.com/company/grapheneos/people/

• 0 California "employees" listed

2. https://www.dir.ca.gov/dlse/SB3_FAQ.htm (I just want to point out that there is a distinction; and I am not a lawyer) "Any individual performing any kind of compensable work for the employer who is not a bona fide independent contractor would be considered and counted as an employee, including salaried executives, part-time workers, minors, and new hires."

It also sounds like they are trying to fill a part-time role. "Must be able to commit to spending 80 hours or more a month" = ~20 hours a week, but given the ebb and flow of release/bug/patch work needed...

FUD

1. GrapheneOS is a non-profit out of Canada.
2. It's an "independent contractor" role. California has specific laws governing the classification of workers as employees versus independent contractors.

I don't know if there's really a better way to manage this need. They need a pretty niche specialized developer, so you have to cast a pretty wide net (globally, mind you) for remote work.

1. It's a pretty small global team.
2. How would they financially/legally manage the burden of tax/benefit/workers rights across all boarders; especially as a non-profit.

Yes, people should know what they are getting into, with independent contractor work. I just think there is (probably) some nuance to this particular case; where hiring people on as an employee doesn't make a lot of sense.

I think you should think about this from a higher abstracted layer of things. The point being; how do you do this in a way that lets you be flexible, no lock in, ease of pivoting, and has the gift of allowing you to do things in stages as your skills/competencies grow. We also want to look to mitigate all sorts of setup/securing/maintenance/update infrastructure complexities and hassles.

1. You're going to have to solve a 'network' problem, how do you securely allow everything to communicate with each other. Managing things like Domain/HTTPS certificates/revers proxies/VPNs/tunnels etc. (Tailscale/Headscale as a solution is complex in and of itself; but the problem spaces it solves for are far more complex, and getting it wrong here can make you very vulnerable, catastrophically)
2. You're going to have to solve a 'user' problem, how do you manage identities, and their ability to authenticate credentials, and use multifactor auth, as well as manage their access to #1 and #3) (IDP, IAM, SSO; is a hard problem, and again, getting it wrong here would be catastrophic)
3. What 'services' am I providing to this network of users/devices? (Storage of things through say Nextcloud/Immich, access to media server for streaming, etc)

For #1 I would lean into Tailscale, and it's features like "Serve" and maybe "Funnel". I don't get the Enshittification vibe, but I suppose it is always a risk. The pivot point, would be to move your coordination server to Headscale. (you still use the tailscale clients, just reconfigured to point to the headscale coordinator).

For #2 Tailscale doesn't do the IDP (Identity Provider) thus all the Logon options. To start like "stage 1" just pick one (my recommendation would be github of the choices available, but also to maybe start investigating git/VCS learning paths), IDP/IAM is a hard problem, you can self host one, but you're adding a lot of complexity, and a huge security burden if you get it wrong. Consider doing this in a later stage; at stage X, work to selfhost something like Headscale/Traefik/Authelia; and then migrating to it to finally ditch all of 'Big Tech'.

For #3 How to host your services; ie Podman or Docker? If your just starting, I'd lean more into Podman; from a security standpoint, as well as a staging things in a way that lets you jump into say Container Orchestration/Kubernetes, (but also if you're worried about enshittification as Docker has shown some of) Adding tailscale to containerized services is fairly strait forward, making them securely available to your 'network'. The docker/podman paradigm is similar enough; learning to do things one way is very similar to the other's way; there is just a nuance to how things actually work, different 'gotcha' things, but a lot of the same abstractions, I don't think it's too difficult to bounce between if necessary.

I don't know that many of my adult friends even hit half the items talked about in this article.
What's your own score?

Who benefits?

Who benefits from sowing a narrative around "drama", "accusation", and/or "paranoia". Seriously.

I think given the following circumspect; GrapheneOS's reaction, to move project pieces out of potential hostile environments/jurisdiction, is perfectly reasonable.

1. France's Support for EU “Chat Control”, scanning proposals. France has been one of the governments most supportive of EU‑level proposals that would require scanning of communications and devices for illegal content.
2. The general French framing and approach to cybercrime. As in other EU countries, French authorities are pushing for: Expanded powers to compel cooperation from service providers, and developers. Strong rhetoric against tools that are seen as systematically obstructing investigations.

Enjoy the journey!
I went with a kit from splitkb ; and the community in their discord was super helpful.
Soldering a keyboard isn't too difficult, the components aren't very fragile, and you mostly have some easy feedback and will know exactly where you messed up (the key doesn't work, which is easier then chasing signals/volts around a more typical soldering/electronics project). I think its a very rewarding endeavor.

I think the harder part is learning a new keyboard layout; and overcoming muscle/finger memory.

The revelations that came out from the Edward Snowden ordeal.

Find the skills gaps that you have; find the thing that interests you about it; and dig into that fundamental piece, don't understand what the fundamentals might be, go check out .edu, or certification outlines with the vocabulary/knowledge you do have so you can build from the concepts (and benefit from their already determined progressions) , so you can developed additional vocabulary and knowledge of the discipline.

I think the gatekeeping part isn't the warning or cautionary advice being given, It's the failure to point, and give direction to, the relevant thing(s), the skill sets, the place to start in order to understand the complexities.

Like the hart-surgeon analogy given elsewhere in the comments; it's not just the dire warning of 'you can kill someone' - it's the humanity to say, well if you want to learn how to do this, you're going to have to start by having an understanding of basic biology, organic chemistry, human anatomy, etc, and to learn about those things go here...

I think you've missed the point OP is trying to communicate. It's not that these things aren't relevant, highly important, and good caution/warning. It's the gate that people are creating with these no depth explainers. "you need to understand" "if you don't know" -- then fail to provide direction to people who want to know, to learn these things, to figure out where to start; that's the gate.

This article kind of reads like a nothing-burger. (and it's buried behind a paywall).

I'm not a big fan of 'tests' that go and try and cherry pick one variable to play around with to make a single conclusion, when it's really the system of various variables working in relation to each other.

The general population, and even general categories of competition, you're better off picking a tire that hits somewhere in the top 20% of performance in all relevant categories: Aerodynamics, Rolling Resistance, Traction (various: stopping power, cornering, surface type, etc), and Durability (mostly related to the additional weight) and making additional compromises as it relates to the thing you are doing, the environment, and your experience.

The price of being on the bleeding edge.
But also, trust the process, it's a feature not a bug.

Also, I'll add, that I think that beginners learning this immutable, devcontainer, distrobox workflow offers you more space to practice and learn by doing. You'll will learn a lot by recovering from some misstep (rollback), and/or by blowing it up, to rebuild it again. (and I encourage you to do it often for the practice and confidence)

Check out the 'dx' variants within universal blue It would be a good time to become familiar with rebasing.

I run bluefin-dx environment. (gnome).

There is a different learning curve to immutable/atomic systems and workflows. I don't think it's harder per say, it's just you'll have to be cognizant of the differences when searching for relative and relevant information when you come up against anything (like any opinionated *nix distro). Learn Homebrew, and Flatpack (and thier quarks running with atomic systems).