I think the reality is that people will downvote the AI posts, and that will incentivise people to not disclose it or outright lie. The other thing that came to mind here is the fact that I've been trying to set my RSS reader up to not show me anything if AI is mentioned. It turns out that I haven't been able to do that because it couldn't discern "AI" from "fair", "pair", "air" etc. but the sentiment was there because I'm sick of hearing about it, and I imagine a lot of people are. This could cause readers or whatever else is configured to block AI content to block the non-ai content too, just because it's mentioned. Additionally it does bring AI to the forefront, which doesn't help with that AI fatigue.
I saw the other thread and decided not to comment because there the conversation was looking pretty contentious, and I didn't want to put a target on my back, but as somebody who almost exclusively posts about my project on Lemmy, I thought that this might be a good opportunity to explain myself.
Due to my project being FOSS, I'm thankful that this 10% rule doesn't apply to me right now because I really don't think I could provide anything useful by spouting my opinions. I do look at questions to see if there's anything I can answer but the community is already great at that and most have more experience and knowledge of hosting infrastructure etc. I don't feel that I have a great deal of insight into what makes for a good self hosting setup, but I have a passion for writing open source software that can be self hosted, and this is the way that I feel I can contribute something meaningful.
I feel that when I post about my project, I am contributing. I'm telling you that it exists, it's free and you're welcome to try or leave it. I do try to keep it relevant so as not to hit anyone over the head with it, and I've put the detailed posts into their own community. Nobody is going to find out that some of these self hosted applications exist if they aren't told about them.
I love that Habitat releases automatically get a mention here now! But just to set the record straight: there is no "anonymous likes" functionality, this will be referring to the change in which you now see a message encouraging you to log in or create an account when attempting to "like" a post. Who knew people actually read the changelog! I'll be more careful with the wording in there going forward.
The inference-scale runtime substrate — resonance mesh routing, Chorus Field participation, agent federation, and protocol-run orchestration — runs on an experimental devnet. Metrics and counters on experimental surfaces may combine live process data with stub or simulated fields.
Are these the forty-one manestically placed grouting brushes that were arranged to feed into the rotor slip stream a mixture of high S-value phenyhydrobenzamine and 5 percent reminative tetraiodohexamine?
Hey, I'm just guessing here because I haven't used Caddy in Docker directly, but I do manage a project that uses FrankenPHP, which is essentially a wrapper for Caddy as I understand it, and I've had a problem that looks similar to this.
Caddy will attempt to generate an SSL certificate, and if you are using a reverse proxy, depending on how it's configured, it will internally attempt to fulfil that certificate generation over port 443, which will fail, because it doesn't have a configured SSL certificate. It's the old catch-22!
The solution I have found is to temporarily internally serve your environment over port 80 for external SSL connections. This will allow Caddy to retrieve an SSL certificate and put it in place. After this, you should then be able to switch back over to port 443 for SSL connections internally, and it'll use the certificate.
Once again -- this is just a guess, and I don't know the exact criteria in getting this going in Caddy, but it might be worth a try. In my FrankenPHP project at least, it was a matter of setting the SERVER_NAME variable to http://${DOMAIN}:80
As far as Lemmy is concerned, I just joined an instance that's relevant to my location (feddit.uk). I suppose if it grew a great deal more popular than that, I could create a community there for my local county.
I should absolutely mention though that I'm still hard at work on Habitat, which is a platform for local communities, and each post has a lat/long location associated for a more hyperlocal type of interaction. It's not on the Fediverse though (though there are plans for non-Fediverse federation).
It is currently not federated, and I should be careful with my words because people often confuse my intent when I talk about this. Federation is planned but ActivityPub is not. More details on this are on github.
Listen, I'm going to shamelessly self promote my project all I can! Also PHP, also Symfony: Habitat is a platform for local communities. I don't think PHP gets enough love! It's incredibly versatile and is actually very fast in recent years.
I feel that there's something you've implied in there that isn't explicit.
For instance:
It makes high-quality posts look the same as low-quality ones.
How does it do that?
that format is not good since lots of people will start to automatically block them
Why would they do that?
You're really going to have to dumb it down for me, and I might not be alone given the number of down votes this post, and your comments get when you mention it.
I've read your comments, I've read the post, and I honestly still don't understand the issue.
Mate! It was you who commented something to this effect on my post a while back! I'm trying to understand what you mean, I really am, but it's not going in. Could you humour me, and explain to me what it is about an image accompanying a text post that makes it bad? Is it that so very often when an image accompanies an article you've seen so many instances of it being low quality content that you're conditioned to assume the same even when it isn't the case?
Hey @sl007@digitalcourage.social. Thanks for the message. I couldn't find any details about Menschys or Fedigeo, I'd love to know more about what you're doing. But just to clarify, I'm not planning to use ActivityPub in Habitat. I've realised recently that using the term "Fediverse" -- and perhaps posting to this Fediverse community has caused some confusion. Additionally, before I looked further into what ActivityPub was, I thought I was going to use it. I was under the impression that any decentralised system would count as "a part the fediverse". Habitat will certainly be federated, but it's possible that it will only be a Fediverse platform as much as email (for example) is a Fediverse platform. I don't plan to write any functionality that will implicitly allow non-Habitat applications communicate with it. I hope that clears things up. My apologies for the confusion, it seems I've confused a lot of people over this and it wasn't my intention.
Yes, this is a good point! I don't necessarily want to slow one Habitat down when waiting for the response of another. It could lock up other requests. If it's possible to send the user the url to retrieve posts with frontend javascript, that may definitely be worth looking into. It sounds like an XSS minefield though, but it could very well be the way to go.
Activity Pub doesn't take advantage of the unique solution we have by knowing the user's location and the location of instances. In a way, it seems overkill for what we want. Additionally, I don't necessarily want other software communicating with Habitat. You never know, I might change my mind as I delve into it. I changed my mind on a great number of things as I came to develop them for phase 1. I accept that there are things about existing protocols that I don't fully understand.
I think the reality is that people will downvote the AI posts, and that will incentivise people to not disclose it or outright lie. The other thing that came to mind here is the fact that I've been trying to set my RSS reader up to not show me anything if AI is mentioned. It turns out that I haven't been able to do that because it couldn't discern "AI" from "fair", "pair", "air" etc. but the sentiment was there because I'm sick of hearing about it, and I imagine a lot of people are. This could cause readers or whatever else is configured to block AI content to block the non-ai content too, just because it's mentioned. Additionally it does bring AI to the forefront, which doesn't help with that AI fatigue.