I loved the idea of GSS but it never caught on: https://gss.github.io/

It’s made by Drew Devault who is mostly well-respected in the hacker community, and it’s made exactly to be an alternative to BigCo-owned source hosts like GitHub, Gitlab and Bitbucket.

which in my mind was the first “replace” version of ripgrep

grep -> ripgrep

sed -> sd

Nope. Nope, nope, nope. Neither C nor Jekyll are dead.

I get the point though -- duckduckgo doesn't provide a browser. But I'm guessing Brave doesn't provide hosted email service (Gmail), file and document hosting (Google Drive and Docs) so the analogy breaks down either way.

That snark being said, I do want more privacy on the web -- so yay Brave!

Second thing is that immortality creates conservatism. Old age does too, but it seems to me immortality over-indexes self-preservation over progress of civilization, where the former is just slightly less of a concern for the individual when lifetimes are as short as they are now.

Most of Africa is not able to trade freely with EU, creating a favorable economic situation for the EU. I'm not sure the milk example is a good one, but historically (post-colonialism) most value gained from mining in Africa has been gained by companies in the EU -- not much value gained for the African countries and citizens. This is due to the lopsided trade agreements but also corporate exploitation of the African countries.

The African countries needs our help in the form of proper free-trade agreements, and in the form of us not meddling with their natural resources.

Source: https://en.wikipedia.org/wiki/List_of_bilateral_free-trade_a...

Comments URL: https://news.ycombinator.com/item?id=25847385

Points: 8

# Comments: 0

It should be noted that Firefox uses the Google banlist as well so switching browsers does not work!

Yes, Haskell is born out of academia. That’s where its strengths come from but also its weaknesses. Many new languages and language features are directly inspired by Haskell’s strong typing and type safety and the world of programming languages is better for it.

I do question whether Haskell will ever be ready for mainstream - probably not. But hopefully some other more practical ML derivative will gain enough momentum to truly become mainstream. Arguably Scala is that language, but Scala feels the C++ of ML-derivatives - the language is too big and the syntax irks me.

Cloudflare Workers as a way of bypassing whitelisted Cloudflare IPs makes a lot of sense, and of course is an attack vector that needs to be mitigated. Now I'm really dreaming – but it would be really neat to have a mechanism similar to LetsEncrypt where you could prove ownership of a domain and allow arbitrary requests to that domain. Given the potential throughput of Cloudflare Workers, it could be valuable as a safeguard even in the current setup (I'm guessing it's possible to amplify one request quite a lot which could annoy a victim server even with if the requests have the wrong `Host`-header?).

You're partially right about the CNAME. The reason I ended up needing workers is to preserve the cookie check that I currently have (implemented in NGINX/Lua) which redirects to app.peergrade.io if a session cookie is set (the cookie is scoped to the top-level domain). Not the neatest, but it used be quite common -- Heroku still does something similar.

I didn't think about Node not being as set-in-stone-standard as The Web Platform and not being sandboxed. An example of where the current setup is awkward would be using `atob` and `btoa` with actual binary data, I had this case when unpacking base64-data in the cookie.

Comments URL: https://news.ycombinator.com/item?id=25057709

Points: 14

# Comments: 3

(Plus, we were in YC batch S17 with the predecessor to Eduflow – Peergrade)

IMO he's still a "rockstar". It's just the Node and JS community that hypes everything disproportionally (they used to at least). The fact that he single-handedly built Apex (https://github.com/apex/apex) show that he's still prolific, and a programmer of note.

There's a similar story for Sindre Sorhus, who moved on from the JS community to Swift.