meteokr

@meteokr@community.adiquaints.moe

• ⁨Comment⁩ on ⁨A self-hosted wiki that can integrate with a fediverse instance⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Ah, if that’s the case then I’ll work on making my own container image based on your ansible implementation. Don’t worry about it, you’re already doing more than I can. Looking forward to the release!

• ⁨Comment⁩ on ⁨A self-hosted wiki that can integrate with a fediverse instance⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  This is extremely cool, thank you for your work! Would you consider supporting a container deployment alongside existing container hosted Lemmy instances? No worries if that breaks to far from your workflow.

• ⁨Comment⁩ on ⁨What makes a content creator an influencer??⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I think it muddies the definition to apply a “goal” relative to their income to either of them. If someone makes content, they are a content creator, without question. Some want to make a living doing it, some just do it because they want to. Both are content creators, regardless of the income. Influencer/CC is a rectangle/square categorization. Influencers are akin to advertisers.

  I completely disagree that a content creator who takes sponsors from other companies, are NOT influencers. If they are acting as an advertiser, then they are influncers, they are still content creators however. If a content creator is just making content and selling their own wares, they are effectively advertising themselves; which is totally fine. If I am engaging with their content, I am already interested in their work.

• ⁨Comment⁩ on ⁨What makes a content creator an influencer??⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  There’s probably more nuance to it, but I consider someone an influencer if they try to sell me something other than their own product. Such as if they try to sell me their merch, that’s still a content creator. Once they take sponsors and try to sell me something else not made by them, then they are an influencer. That’s where I usually draw the line.

• ⁨Comment⁩ on ⁨Do any of you use Raspberry Pi’s ?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I use a Pi4 to run one of my HAproxy nodes. It does die once in a while from not enough power because my power brick is pretty old at this point. Other than that its great. I used to have a cluster of Pi3’s bit I’m transitioning cluster managment systems so they aren’t doing anything right now. I recently got a Lichee pi and that will most likely replace them once I get it all working.

• ⁨Comment⁩ on ⁨Certificate management⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  It is primarily a http server, its ability to act as a http reverse proxy is a product of that. Apache can do the same thing, its just less common to see it used that way.

• ⁨Comment⁩ on ⁨Certificate management⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Probably not the ‘recommended’ way, but I use a selfsigned cert for each service I’m running generated dynamically on each run with nginx as a reverse proxy. Then I use HAproxy and DNS SRV records to connect to each of those services. HAproxy uses a wildcard cert for the real domain and uses host mapping for each subdomain.

  This way every service has its traffic encrypted between the HAproxy and the actual service, then the traffic is encrypted with a browser valid cert on the frontend. This way I only need to actually manage 1 cert. The HAproxy one. Its worked great for me for a couple of years now.