Thank you, I started Godot recently and I'll take a look at Defold as this is the exact thing I am doing - and Godot seems a little unstable with the APIs. Every tutorial I find is for Godot 3, and Godot 4 seems quite changed.

The version 3 to 4 transition was used to make breaking improvements to many things. The API is intended to remain stable within major versions. The docs also cover the major API changes from 3 to 4 and comprehensive docs exists for both version and you can still use Godot 3 if you want to.

google "godot 4 tutorial", not "godot tutorial"

As much as I love Flask (or Bottle) and the Go approach, I find myself in the same boat.

Curious question, why you say Django is mostly anarchy compared to Rails? I haven't used Rails btw.

Django has a few features that can be taken for granted: the ORM, the templating language (ouch), the admin, the user/auth/permission system, the division in views (called controllers in Rails) and templates (called views in Rails.) They are well known entities but there is no well defined structure for the code. A project can have any shape and I've seen no two projects with the same shape. On the other side every Rails project has the same shape, often even across multiple versions of the framework. The greatest departures from the standard are some app/services directories but in general you can tell where a url is implemented without looking at Rails' equivalent of urls.py

Django allows multiple subprojects inside an app and code wherever one wants to place it. Rails also allows code anywhere but in practice it's always in the same places. Maybe it's Python, inviting developers to overengineer their code.

Ah that's a super explanation there, thank you!

Yeah the templating language is not so nice, I sometimes use Jinja instead. Also, I don't like the classic MVC so I have a completely different structure thus validation your point completely :P

If you ever end up in Django land (for some project), checkout Django Ninja for APIs, you'll end up avoiding having these annoying url files and just have a

@api.get("some/api") def some_api(request):

instead. Super simple and useful. I just recently discovered it and I don't know how stable it is but it seems pretty stable so far.

I was thinking of building exactly this type of thing here. This is great and I love the simple/minimalistic styled pages.

Things I was also contemplating to implement you can freely steal:

1. Giving a list of potential interesting investments - these could also be behind paywall.

2. Summarize based on sectors to see where there's downturns coming - again maybe paywall this

3. Connect with news-sites or twitter etc.. to see what is happening and what is the sentiment. This is a lot harder as you'll need to either scrape or pay to get that info.

Best of luck

Really nice of you to encourage, thank you! I've thought about some of those.

The first one is an interesting idea, but offering any real financial advice is regulated, which is a tread carefully territory

Second one is achievable and a good one at that. In fact, there is a lot of canonical data out there that when used carefully can provide a very nuanced picture of the current state of economy.

Third one, currently I have just a twitter account where the earnings reports are auto posted the second they are ready (that is, until I run out of free api limits). Their API cost for at the higher end makes it only viable if I am doing it full time and there was a clear edge by analyzing the data. My gut feeling is, most of the work will go into filtering out low signal posts idk

I'd suggest moving to either bluesky or rss. In fact, selling rss access (very fast responses) and delaying the public (twitter/Bluesky) releases by a few hours/days may be a way to monetize successfully.

Unpopular opinion here... If you tread carefully you'll most likely not succeed. I am not American and I know you guys like to sue eachother for putting cats in microwaves and stuff so maybe this is not great opinion to have in America at the current moment.

I would go for it and put a disclaimer, or I would just incorporate in a country where there's no issues with these things.

all this is hard of course to provide good value, but worthwhile.

Twitters' cost is insane right now, I had quite a few ideas for twitter integrations but they would easily cost thousands per month just to access their API.

I looked into https://github.com/d60/twikit - might not be suitable but you can definitely play around with it. Just don't use your official account as I got shadow banned using it unfortunately.

>Unpopular opinion here... If you tread carefully you'll most likely not succeed. I am not American and I know you guys like to sue eachother for putting cats in microwaves and stuff so maybe this is not great opinion to have in America at the current moment.

It's not actually about personal suits, financial advice may fall into financial services regulations and that's regulated by the government of the US, EU, etc. so wherever the company is registered may have issues in addition to the potential of the regulations applying to the individual and not shielded by the company.

Was figuring out how to do the same thing, but for an Indian context, and specific to one's portfolio, by perhaps reading emails. Was still ideating it, cause I am working on another thing at the moment.

I'm interested in this topic too, but am approaching it from an auditing rather than from an investing angle.

Facebook found the solution to all these shenanigans

I absolutely love Caddy. Used it for years. Very reliable and so easy to setup once you learn the basics. The documentation is a bit hard to get, but it saved me so much time and energy compared to trying to get letsencrypt working reliable ontop of NGINX.

I used Caddy for a couple of years but eventually went back to Nginx.

For the Let's Encrypt certs I use certbot and have my Nginx configs set up to point to the appropriate directories for the challenges for each domain.

The only difficulty I sometimes have is the situation where I am setting up a new domain or subdomain, and Nginx refuses to start all together because I don’t have the cert yet.

It’s probably not too complicated to get the setup right so that Nginx starts listening on port 80 only, instead of refusing to start just because it doesn’t have the cert for TLS needed to start up the listener on port 443.

But for me it happens just rarely enough that I instead first make the config and outcomment the TLS/:443 parts and start it so that I can respond to the request from Let’s Encrypt for the /.well-known/blah blah stuff, and then I re-enable listening on with TLS and restart Nginx.

I also used DNS verification for a while as well, so I’m already aware that’s an option too. But I kind of like the response on :80 method. Even if I’ve managed to make it a bit inconvenient for myself to do so.

I tried to setup Caddy last year as a reverse proxy for all paths matching "/backend", and serve the rest as static files from a directory. I had to give up, because the documentation was not good enough.

I tried the JSON config format that seems to be the recommended format, but most examples on Google use the old format. To make it even more complicated the official documentation mentions configuration options, without informing that it requires plugins that is not necessarily installed on Ubuntu. Apparently they just assume that you will compile it from scratch with all options included. Lots of time was wasted before I found a casual mention of it in some discussion forum (maybe stack overflow, don't remember). I just wanted the path to be rewritten to remove the "/backend" path before proxying it to the service. I guess that is uncommon for a reverse proxy, and have to be placed in a separate module

I may appear overly critical, but I really spent a lot of time and made an honest attempt

I'll go back to nginx. Setting up let's encrypt requires some additional steps, but at least it's well documented and can be found in Google searches if necessary

Huh, sorry that it was that difficult. Based on what you wrote, this should suffice:

    example.com
    
    root /etc/www
    reverse_proxy /backend/* 127.0.0.1:8080
    file_server

It seems simple, but I used the JSON format which seems to add a lot of complexity (basically serialized version of objects)

I also had to install a separate module just to get a decent access log...

Could be my fault for going too far down a wrong path, but it could also be a sign of poor documentation

I found my last attempt here (before I gave up). I also spent a lot of time getting the basic logs working, by installing modules that wasn't part of the standard distribution

    {
      "logging": {
        "logs": {
          "default": {
            "level": "INFO",
            "encoder": {
              "format": "transform",
              "template":"{common_log}"
            },
            "writer": {
              "output": "file",
              "filename": "/var/log/caddy/access.log",
              "roll": true,
              "roll_size_mb": 5,
              "roll_gzip": true,
              "roll_local_time": true,
              "roll_keep": 5,
              "roll_keep_days": 7
            }
          },
          "dev_access": {
            "level": "INFO",
            "encoder": {
              "format": "transform",
              "template":"{common_log}"
            },
            "writer": {
              "output": "file",
              "filename": "/var/log/caddy/dev_access.log",
              "roll": true,
              "roll_size_mb": 5,
              "roll_gzip": true,
              "roll_local_time": true,
              "roll_keep": 5,
              "roll_keep_days": 7
            }
          },
          "errors": {
            "level": "ERROR",
            "writer": {
              "output": "file",
              "filename": "/var/log/caddy/error.log"
            }
          }
        }
      },
      "apps": {
        "http": {
          "servers": {
            "srv0": {
              "listen": [":443"],
              "logs": {
                "default_logger_name": "dev_access"
              },
              "routes": [
                {
                  "match": [
                    {
                      "host": ["<redacted>"],
                      "path": ["/backend/*"]
                    }
                  ],
                  "handle": [
                    {
                      "handler": "subroute",
                      "routes": [
                        {
                          "handle": [
                            {
                              "handler": "rewrite",
                              "strip_path_prefix": "/backend"
                            }
                          ]
                        },
                        {
                          "handle": [
                            {
                              "handler": "reverse_proxy",
                              "upstreams": [
                                {
                                  "dial": "localhost:8080"
                                }
                              ]
                            }
                          ]
                        }
                      ]
                    }
                  ]
                },
                {
                  "match": [
                    {
                      "host": ["<redacted>"]
                    },
                    {
                      "file": {
                        "try_files": ["{path}", "/index.html"]
                      }
                    }
                  ],
                  "handle": [
                    {
                      "handler": "file_server",
                      "pass_thru": true,
                      "root": "/home/server/web/dist"
                    }
                  ]
                },
                {
                  "match": [
                    {
                      "host": ["<redacted>"]
                    }
                  ],
                  "handle": [
                    {
                      "handler": "rewrite",
                      "uri": "/index.html"
                    }
                  ]
                }
              ]
            }
          }
        }
      }
    }

> I had to give up, because the documentation was not good enough.

I had the same experience. And also somewhat bothered me that even a very basic and common functionality like rate limiting is not built-in.

Sounds like last example here?

https://caddyserver.com/docs/caddyfile/directives/handle_pat...

There are already full solution for things like that i.e. https://github.com/linuxserver/docker-swag

I don't get it as well, though I think the situation is classical regulatory capture. In other words, the wrong regulation.

I like the style the Czech/German system is doing healthcare. It is public but kinda private. You pay to the government, but you decide where to go so the hospitals/doctors compete for your money. It is very different than the centrally planned Danish or English based where there's basically some person in top that decides everything.

I am Czech. I do not have dentist or GP, they are overloaded, none are taking new patients! I have to pay private treatments out of my own pocket! Alternative is to spend like 30 hours calling and calling, and then wait 3 months for an appointment at dentist!

I am forced to pay about 500 euro on mandatory public health insurance (tax) every month!

The same is true in my city in the US, though. My dermatologist schedules 6+ months out for new patients; cardiac/neuro is 3-9 months depending on the urgency. Most of the primary care practitioners in the area are full up; I see regular posts on the local subreddit looking for anyone, anyone taking someone.

And also where the industry that's supposed to be regulated is reverse-dominating the regulatory agencies. Maybe par for the course in other industries too, but they have powerful lobbying groups like American Hospital Association.

It has NOTHING to do with regulatory capture.

The US is polarized with the republicans not wanting any socialized health care because they don't want to care for people not like them. You can't organize and correctly run a health care systems when half you politicians actively sabotage and burn it down.

> not wanting any socialized health care because they don't want to care for people not like them because they don't want to care for people not like them.

Categorically, older individuals tend to vote more conservative and more republican. This doesn't make sense to me at all.

What makes more sense is that they argue against the socialization of any industry that funds their campaigns.

Democrats seem to take a more middle ground. ie Obamacare socialized low cost solutions and pushed costs uphill toward people who need more expensive care.

Do you really think politicians are motivated by "not wanting to care for people not like them"

That's such an insane assumption to make.

Do you live in the US? There were supporters of a certain party complaining that the president wasn't hurting the right people fast enough..

That is your perception, I'd bet if you asked those people they would disagree with your synopsis

Oh man, I needed this so many times didn't even think of doing it like this. I tried using Selenium and all different external services. Thank you!

Works in chromium as well.

Same here. I just gave up on most of these websites. When I absolutely need to use a website such as for flights, I have a clean chrome browser I spin up.

I ended up on Fedora which seems similar to the "old ubuntu" where things just works. Stability can be a problem as they update quite often.

If you explicitly use "-e ssh" and don't run a daemon, then these probably don't affect you.

If you don't specify that protocol, though, you have three scenarios:

1. only the local host has the rsync binary 2. both local and remote hosts have the binary, but neither runs them as a daemon 3. both have the binary and the remote runs as the daemon

In #1 you end up using SSH anyway (unless there's also no SSH binary). In #2, a malicious server binary could attack you. In #3, a malicious server binary could attack you.

Also, many of rsync's features rely upon both sides having the binary.

Wow, thank you - this is exactly what I didn't get. You explained it super well.

I am number 2, and so I guess it wont affect me as long as the fingerprint doesn't change to a malicious server that have taken over an IP.