ether+nick

@wjmaggos @quillmatiq Oh I wouldn't say it's *wrong*, it's normal I think for people to want others to use and be on and post on the social network they're using and to try to convince them to what they believe in, just like I'm trying to do in the other direction 🙂

@quillmatiq @mackuba

lots of telling people how to use tech is overblown imo, but I don't think people are wrong re the negative social implications of big tech, like using X or substack. or the YouTube algo. I think Trump won mostly thanks to boomers and Facebook algo.

I'm glad you're trying to give people a way out but I think the business model will account for that. imo VC history shows they will "go evil" and I can't see how it's wrong to try to convince people to just build here instead.

@wjmaggos I'm trying not to tell people how to find their communities and instead focused on helping them do that while also giving them tools to change their minds on how they do that if they want to.

@mackuba

@quillmatiq @mackuba

capitalism does this automatically. afaict you're trying to bend that curve for what you see as a humanitarian purpose.

government regulation tells people how to live their lives and builders how to run what they built. we should be willing to do something to oppose rampant enshittification, right? the wealthy having more influence over our government?

@wjmaggos I'm not in any business, I'm behind the purpose of connecting folks to their people without having to tell them how to live their life or telling builders how to run what they've built.

@mackuba

@evan @Em0nM4stodon I have a somewhat similar setup, but grouped by infrastructure - one domain that hosts everything on a web space (e.g. a CMS and other small things). Things there are either separated by path or with subdomains.

A second one for everything that's hosted on my VPS, where everything lives on its own subdomain. It's the same name, but on another tld. I did this, because setting up every subdomain as a DNS record manually on my Webspace was a PITA. Now I just have a wildcard pointing to my VPS and the reverse proxy takes care of the routing to the services.

And about a year ago, I got a third one, which I use for everything on my homelab. On the internet it just resolves to 127.0.0.1, but the local DNS resolver in my network will happily resolve all the entries to containers/VMs. Side effect: With Let's encrypt and DNS-01 I now have no more self signed certificates at home and no personal CA to run.