So far I see more value in ontologies than graph databases. When using established ontologies naming does not become an issue and exchanging / understanding data becomes easier. You also push some of your code to the database "as data" and can reason on it better.
We are actually working with semantics / ontologies. The graph database is just our engine for storing the data. I am starting to think whether an ordinary SQL database could be just as useful.
Very interesting. What did they used to use back in the day? SPARQL? This wiki article indicates that it should be possible to store triples in a RDBMS
Replying to a complaint about low-effort comments with your own low-effort comment? Brave effort, but you'd be doing everyone a favor to stop doing one-line middlebrow dismissals that have been done here at least a thousands times before. It's not creative nor interesting, which I hope is why most of us are here in the first place. I may agree or not with you, but it simply doesn't make for a good reading of the comments to hear the same thing over and over again...
Hetzner does not open port 25 outbound (SMTP) until you have paid your first invoice. I therefore believe them to handle this problem somewhat seriously.
I had great fun setting up Postfix and Dovecot recently.
However, I was very specific with always going for the minimum most simple solution. I do not have a dedicated database for instance, but use just mbox and POP3.
And I did not even bother much with anti-spam, I chose a super easy filter in Thunderbird instead, sending everything with 'unknown' in Received: header to the Thrash folder.
Getting accepted by others was also not much of an issue (but lots of details of course, PTR, SPF, DKIM, DMARC).
> And I did not even bother much with anti-spam, I chose a super easy filter in Thunderbird instead, sending everything with 'unknown' in Received: header to the Thrash folder.
I realise that everyone hates spammers, but having a "thrash" folder is a bit much, isn't it? ;)