AgoRapide

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.

So the easy "instant" graphs offered by Cypher engines are just temptations then?

Looks like a SQL foundation and a solid database engine is better (as always).

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.

Maybe because blockchains are just a Ponzi scheme while Facebook may have some actual value?

Works quite fine for me (Chrome)

I just use Notepad in Windows, and store everything in a single document.

This single document also contains my diary / log for daily activities.

Plain text is enough for me.

Average is not the same as mode. 99.9% of people (at least) have more arms than the average for instance.

So yes, theoretically 80% may be better at driving than the average, it is just so that the other 20% are even worse at it.

I just switched from EC2 to Hetzner. I found Hetzner's approach much more customer friendly, you set up PTR yourself for instance.

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).

More details here if anyone is interested:

http://bef.no/DitchingWindowsAndAWS/

I have dabbled with the same problem with AgoRapide which offers queries through GET (although on a much simpler level than PQL / GraphQL).

I just present the query in readable form together with the output, letting the user choose between copy / paste the URL or copy / paste the readable form.

Example:

http://arnorthwind.agorapide.com/RQ/dt/Order/WHERE%20Shipped...

will present the alternative form

   Order

   WHERE ShippedDate = Today

   SELECT OrderId, ShippedDate, CustomerId, Customer.CompanyName, OrderDetail.Sum.Sum() AS SumOrder

See more examples at http://arnorthwind.agorapide.com/

Thought so. I always wanted to build such a system, but usually end up recommending some sort of cloud service instead.

Did you notice that the demo site is throwing an HTTP 500 error?

No... Looks OK to me.

ORM = Object-relational mapping.

Never used it. First time I was introduced to an ORM (Hibernate) my instinct said to run away. Just too much complexity involved for little gain.

I usually find that my projects are well suited to key-value storage, often with a natural chronological order. In other words: A complex RDBMS table structure is not needed anyway. This again reduces the need for any ORM.

Regular expressions.

Functional programming.

I run an IoT company where we do customer management without any special RDBMS system at all, I just built an HTML interface into the JSON API which in turn is mostly exposing a key-value store.

Not sure if this would qualify as a full blown customer management system though, although it does covers concepts like Customer, Gateway, Device, Payment, Notifications / Alarms, Support incidents.

Currently this has almost only a single-company use, but I would love to see other use the same concepts.

See https://bitbucket.org/BjornErlingFloetten/ARCore for more details. See http://arnorthwind.agorapide.com/ for an easy to grasp demonstration.

Self promotion: With my library AgoRapide 2020 the client can choose between HTML or JSON, with HTML giving useful links.

An example with Microsoft's Northwind dataset:

http://arnorthwind.agorapide.com/RQ/dt/Employee/1

gives HTML output with helpful links, in this case related EmployeeTerritories and related Orders.

The same query in JSON

http://arnorthwind.agorapide.com/RQ/dt/Employee/1.json

will show data for the Employee only.

This kind of turns the API into a client application, that is, you do not necessarily need to build a user interface on top of the API, it is actually inbuilt in the API.

The main customer support application in a IoT company that I run is just such an API. The customers themselves of course are offered a real app on top of this API, but not having to maintain a dedicated application for the support department is a huge saving.

It is nice to get some reminders why I still use a so called 'dumb'-phone.

Very easy to use and with extremely long battery life.

And if I lose it or damage it, the replacement cost is a non-issue. I had a Nokia costing 79 NOK (approx USD 10) for over ten years. Eventually the screen died. Now I am using my daughters old Nokia, which I got free of charge because she swithced to Apple.

And even better, the kids can not demand 'better' or more expensive phones than what I use myself. That is where the big savings are :) :) :)

Good point, even more so because I use VLC myself because of the exact same reason, it plays anything. I just never thought of giving it URLs, only local files.

(But the user interface in VLC sucks though...)

I was very limited with regard to time available.

With one baby, one toddler and three more kids around there is not much free time :)

I would love to put a Raspberry Pi inside an old radio myself.

Not nearby, that was the original problem.

Never took the effort to reduce it to standard Internet size. But I will if I get 10 000 hits on the page tomorrow too. Amazon wants its dues.

Yes, it looks really cool, expensive but cool.

Hear! Hear!

Yes, I could.

It would not have been so fun. And all Internet radios I have seen so far have some features that irritate me. For instance volume is push-buttons instead of turning knobs.

Actually, the only interface I would have on a radio is two turning knobs, one for volume and one for channel.

Thats all. The rest could be some phone or PC setup like 'kingsuper20' suggested.

Too sad Apple never gave us a radio. I might have been an Apple customer if they had.

I would link to implement https since almost all other sites I surf on now are https by default.

But the last time I tried it with multiple domains pointing to the same server it was too cumbersome.

And having to renew the certificate is also not very appealing for a small hobby site.

Yes

By the way, while we are discussing readability, important message to all hipsters: We boomers prefer high contrast, that is black text on white background.

Sites with grey text on grey background I usually skip.

Once Firefox was my web browser because it has a very easy setting for forcing exactly this (black on white).

Author here. I took a look in IIS Admin and is unable to see WHERE did I ask it to serve https. I thought I was http only. The bindings only say http, both for the bef.no site and for the 'Default Web Site'.

I am reading this, just been busy with some errands last hour :)

Thanks for the tip, a dedicated application in combination with Stream Deck sounds even better.

I do not agree with the tablet thing. Too many things can go wrong, and tablets are touch only, no tactile feedback.

But your last idea was actually an excellent suggestion :) An ideal hacker project!

Thanks for the information, I will considering getting myself a SSL certificate. I did not knew this to be a problem until now.