apeacox

watched them live last year in Teatro Antico di Ostia, wonderful show to see them live, worth the ticket price.

I also remember your articles on Linux&C about buffer overflow, sockets in C, etc... ;-)

Not a monopoly, but a walled garden.

Exactly, they aren’t exposed outside. That’s why you can “potentially” add rules to route request from the outside to an internal host:port, even 80/143. On the LAN you would still able to connect to router admin.

DNAT. You map one/more ports from your router exposed on internet to ip:port of the local app.

However, http/https ports are already used on routers to offer an admin web GUI. It’s technically possible to circumvent this with some ad-hoc firewall rules, but it depends if the router admin UI let’s you do that.

Other than going deeper with Elixir knowledge on new problems (see below), I learned and brought in production the followings:

## DevOps

* AWS Cloudflare and Lambda (with Go)

* Kubernetes

* Ansible and Terraform

* deploys from gitlab/bitbucket pipelines

* production/dev setup with Docker and docker-compose

## Patterns

CQRS and Event Sourcing

I’m going to continue on these paths during 2019, maybe with some new stuff as well.

Yes, you can definitely connect manually through telnet (I did it back in the old days). The only problem is it will not stay connected too much, because you should also reply to server's PINGs at regular time intervals otherwise you'll get disconnected.

> This could have been avoided, but the time to avoid it was perhaps in the early 2000s.

there were protests, from Seattle '99 until Genova '01, where many different groups merged into a single protest agaist that kind of globalization. but after 9/11 everything almost vanished in the name of worldwide anti-terrorism.

I suppose through some kind of machine learning, given the fact that they have a miriad of data of any kind.

It might look like a funny experiment/excercise for someone at Google.

I'm hosting Gitea on a $5/month DigitalOcean box, I had to setup disk snaposhots and db backups for security.

It's running since a year, never had a problem with it. It only consumes 20MB of RAM and is extremely fast. Easy to deploy (I've used ansible)

Hopefully without mining and selling user data. This might be the real killer feature.

Read books and articles. Read and write a lot of code by trying to solve a problem. When you have a problem, study to solve it in the best way possible (that even means rewriting from scratch if you think so). Try to deploy a complete product online in some way, even the simplest one. This should help finding the spot that fits better for you. For example, working on frontend or backend, focusing on security or UX... there are a lot of specific topics you might want to dive into based on your tastes. After some time, you’ll be able to drive your knowledge by your own. Asking now will not help that much.

Good luck ;-)

You’re just trying to impose your opinion. Speaking about sex or even a love relation is not shitty. If you’re triggered with it, all I can do is avoiding to talk about it in front of you in person. In all other cases it’s your problem, not mine.

Maybe it’s creepy for you or a bunch of others. I find it funny, at least until it’s used with caution and in the right contexts. We’re adults, sex and technology (along with a lot of other things) are parts of our life, I really don’t see the problem here.