purge

a ground-up rewrite of the popular GraphQL API from schema builder

I send money to 'the third world' a lot and it's extremely easy without having to resort to crypto nonsense. Hearing these implausible points repeated every time this question comes up just seems desperate now.

postgraphile v5 has significantly improved query generation (https://postgraphile.org/postgraphile/next/) since moving to grafast (https://grafast.org/grafast/)

many of these concerns are mitigated by ensuring you are using trusted documents (https://benjie.dev/graphql/trusted-documents)

it requires a meta sign-in, which isn't a facebook account.

they made the change from any to unknown in the catch handler so its not without precedent

I love postgraphile and the graphile toolkit (worker and migrate are best in class imho).

The second screenshot is from windows 2, which was released in 1987

I'm not sure about the peering connections but Uganda does have a good range of ISPs (outside of Kampala connectivity is mobile network only).

The mobile providers are:

- Africell (was orange)

- MTN

- Airtel

- Smile

- Uganda Telecom

This is good to know about (and a great idea) - i'll take a look later. The other issue with using a VPN is people can no longer use the 'social pack' which is a cheap social media only data package available on all the networks.

I'm living in Uganda at the moment and have a couple of things to add:

1. VPNs still work fine (I'm using one right now, though its one I installed on a digitalocean instance - it's possible those receiving lots of traffic have now been blocked).

2. This tax is unaffordable for many Ugandans (it would be about 5% of the average wage here). Whatsapp is very popular here and this has impacted everybody I know. Most people I've talked to are using a free VPN (they aren't aware of the risks here).

I haven't done much analysis of the blocking yet but I will be doing a more in-depth post about this whole debacle in a few days.

The backend API is indeed (modern) Perl and the repository is here: https://github.com/metacpan/metacpan-api

full history of Symantec CA issues: https://wiki.mozilla.org/CA:Symantec_Issues

SEEKING WORK - Brighton / London, UK. Remote.

Experienced freelance dev React and React Native.

Backend node.js / postgresql / graphql / REST

Email: [email protected]

Web (updating soon!): http://papercreatures.com

I feel I should do the obligatory Dan Carlin link here: http://www.dancarlin.com/product/hardcore-history-50-bluepri...

Long, harrowing and left me hankering for more. He covers Verdun in the later episodes.

We had issues every few months because the server we were assigned would be added to a RBL. Customers would notice, we'd talk to Mailgun and they would move us to another server. rinse, repeat.

The only way to avoid this was to get a dedicated IP which is an additional $59 / month.

I'm not sure why Mailgun couldn't detect this themselves, maybe they do now.

I don't understand how this scam was realised then. They must've managed to get access to the applicants true email address somehow?

One of my friends was caught out by a similar scam last year. There is plenty of prior art for airbnb to look at when developing a safe platform for people to communicate through. At the very least they should disallow exchange of e-mail / non-airbnb websites via the platform communication channels.

This has been the single best investment i've made to my workflow for years. Really communicative, friendly developer too.

I was somewhat dumbfounded when I was asked for my apple id and password when I went to get my screen replaced at the apple store.

After some debate with more senior team members, I reset my password to something generic and gave it to them, but it sets a bad precedent for customers who should be educated into never giving their password, under any circumstances.