• 4 Posts
  • 186 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle





  • Yep and the slow gutting of the education system isn’t making it any better.

    You have an entire generation coming of voting age who are rabid Trump supporters. They don’t care about policies or democracy or public institutions. They don’t care about healthcare, social securities, or the stability of the economy.

    They don’t care about any of the things that have been built up through generations. They lack critical thinking ability.

    The recipe works. If you make dumb kids they will vote for dumb people. It works so well that part of the future plan for a trump presidency is to get rid of the department of education. Solidifying the Republican party indefinitely.

    Without critical thinking and with mass media it’s so easy to say every problem that people deal with is because the “other side” made it so. Even if the other side has been doing everything possible to achieve the opposite.



  • I… That’s not how this works. Or at least that’s not the context I’m referring to.

    I can make an account (or 1000, Lemmy doesn’t exactly have controls to stop me) and run it as a bot, and NOT mark it as a bot. And use it to automatically manipulate the tone of conversations and threads without anyone knowing. And the premise of your argument is now void.

    Labeling of bots is done via goodwill.

    We’re not worried about goodwill users in this context. We’re talking about astroturfing bots posing as actual users. That said, labeled bots are still a problem if their content out grows organic user content, since that just isolates us, and erodes our community in favor of w/e interesting content bots scaped up today.

    Which is a massive problem on almost every social media platform already. And will come to Lemmy soon enough.




  • douglasg14b@lemmy.worldtoSelfhosted@lemmy.worldMozilla grants Ente $100k
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    2 months ago

    The issue here is that these are solvable problems, release compat isn’t a new problem. It’s just a problem that takes dedicated effort to solve for, just like any other feature.

    This is something FOSS apps tend to lack simply due to the nature of how contributions tend to work for free software. Which is an unfortunate reality, but a reality none the less.


  • douglasg14b@lemmy.worldtoSelfhosted@lemmy.worldMozilla grants Ente $100k
    link
    fedilink
    English
    arrow-up
    34
    arrow-down
    3
    ·
    2 months ago

    People really underestimate the value of stability and predictability.

    There are some amazing FOSS projects out there ran by folks who don’t give a crap about stability or the art of user experience. It holds them back, and unfortunately helps drive a fragmented ecosystem where we get 2,3,5 major projects all trying to do the same thing.



  • Because the majority of my traffic and services are internal with internal DNS? And I want valid HTTPS certs for them, without exposing my IP in the DNS for those A records.

    If I don’t care about leaking my IP in my a records then this is pretty easy. However I don’t want to do this for various reasons. One of those being that I engage in security related activities and have no desire to put myself at risk by leaking.

    Even services that I exposed to the internet I still don’t want to have my local network traffic go to the internet and back when there is no need for that. SSL termination at my own internal proxy solves that problem.

    I now have this working by using the cloudflare DNS ACME challenge. Those services which I exposed to the internet cloudflare is providing https termination for, cloudflare is then communicating with my proxy which also provides https termination. My internal communication with those services is terminated at my proxy.



  • I stated in the OP that cloudflair HTTPS is off :/

    I’m not using cloudflare for the certificate. I also can’t use the cloud for certificate anyways for internal services through a loopback.

    Similarly you can have SSL termination at multiple layers. That’s works I have services that proxy through multiple SSL terminations. The issue that I’m having is that the ACME challenge seems to be having issues, these issues are documented and explained in various GitHub threads, however the set of solutions are seemingly different and convoluted for different environments.

    This is why I’m asking this question here after having done a reasonable amount of research and trial and error.


  • I am doing SSL termination at the handoff which is the caddy proxy. My internal servers have their SSL terminated at caddy, my traffic does not go to the internet… It loops back from my router to my internal Network.

    However DNS still needs to have subdomains in order to get those certificates, this cloudflair DNS. I do not want my IP to be associated with the subdomains, thus exposing it, therefore cloudflair proxy.

    You’re seeing the errors because the proxy backend is being told to speak HTTPS with Caddy, and it doesn’t work like that.

    You can have SSL termination at multiple points. Cloudflare can do SSL termination and Cloudflair can also connect to your proxy which also has SSL termination. This is allowed, this works, I have services that do this already. You can have SSL termination at every hop if you want, with different certificates.

    That said, I have cloudflair SSL off, as stated in the OP. Cloudflare is not providing a cert, nor is it trying to communicate with my proxy via HTTPS.

    Contrary to your statement about this not working that way, cloudflair has no issues proxying to my proxy where I already have valid certs. Or even self signed ones, or even no certs. The only thing that doesn’t work is the ACME challenge…


    Edit: I have now solved this by using Cloudflair DNS ACME challenge. Cloudflair SSL turned back on. Everything works as expected now, I can have external clients terminate SSL at cloudflair, cloudflair communicate with my proxy through HTTPS, and have internal clients terminate SSL at caddy.