Scrolling up they recommend avoiding Purism hardware because

> In particular, the Intel Management Engine is a severe threat to privacy and security, not to mention freedom, since it is a remote backdoor that provides Intel remote access to a computer where it is present.

However, the Intel ME has been disabled in Purism hardware since 2017.

https://puri.sm/posts/purism-librem-laptops-completely-disab...

Pretty sure that write up was done around 2009

Just to clarify and save anyone else from the ambiguity - it looks like TFA should be tagged [2009], while parents link from Pusim is more recent (2017).

...which was written in 2015, so also outdated.

Long time user of Firefox on desktop, but recently moved away from Firefox on android after reading that it's "much more vulnerable to exploitation and inherently add a huge amount of attack surface".

https://grapheneos.org/usage#web-browsing

I rarely come across a piece I disagree with so vehemently, at such a core level.

My conclusion is rather: The politics of the Anthropocene will be democratic and horrible.

This article has pushed me more firmly into the re-naturalization camp of politics, economics, and nature.

I enjoyed reading it though, nice to see someone actually thinking about these things and not just being touchy-feely.

Agree, there's clearly more left-leaning stuff on here than other positions.

Copyfree, but still lawyer-y:

http://coil.apotheon.org/

Seems a nice effort, but the "necessarily infringed" seems awkward (if there's a license, there's no infringement!). Has it been reviewed by an IP lawyer?

Dunno, but I think so. It's on this list:

http://copyfree.org/standard/licenses

I'm sure the people on ##copyfree over at irc.freenode.net know more than I do.

Compare: https://licensezero.com/licenses/charity

Yeah, the coil is much more lawyer-y than that one.

I prefer copyfree licenses

http://copyfree.org/

and usually release stuff under the Copyfree Open Innovation License (COIL)

http://coil.apotheon.org/

I read that entire front webpage and still have no idea what a copyfree license is.

Not having a server at all is the easiest. I run my front ends on S3 / CloudFront. Backend is run on Lambdas, with state stored in DynamoDB/SimpleDB (can't wait for serverless Aurora though!).

create-react-app and aws-amplify gets you really far in a hurry.

I then normally use react-redux, @redux-offline/redux-offline, react-router-dom, and flow-bin.

Examples: - https://gitlab.com/kabo/synchronize-swatches - https://gitlab.com/kabo/hydrant-map - https://gitlab.com/kabo/cryptodo

For more backendy stuff I use serverless to manage lambdas.

Easy as :)

as a frontend dev new to this stuff - how do you keep your lambdas secure? literally anyone can see your secrets?

I'm gonna go through your code, thanks for sharing, just wanted to ask in case you have a big picture insight about how serverless auth/security is best done. this stuff freaks me out because i know nothing about it.

I'm afraid I don't follow. What secrets are you referring to? Secrets in the code running on the lambda can't be seen by anyone. If you mean secrets to invoke the lambda I usually have lambdas be completely open (no auth required) or have users log in with cognito and use aws-sdk invoke the lambda, which takes care of auth for me.