No, I assume that the bots would only repost the most highly voted content. If a bot were to post everything, including low-quality content, the moderators could simply ban it.
As for having the bots in another instance, people are going to go to the instance with the most content, and that would be the bot instance. Do we really want to drive the users away?
As for different communities, people who don't want to see bots can disable them in the user settings, so the communities wouldn't change for them. I don't see the point in having bot communities.
I don't agree that a bot would steal content. Content creators need exposure and they post for free on Reddit, so why wouldn't they want the same here?
There is a list of federated and blocked instances on the bottom of the page. https://latte.isnot.coffee/instances
Also this script is to see which instances block or are blocked by the instance you choose.
I'm honestly more confused than I was before. With so many opinions, I don't know how this could ever be implemented in a way that satisfies people.
> Microsoft Research has developed Orca, an open-source project that introduces a progressive learning model based on GPT4. This model achieves impressive performance comparable to GPT 3.5 and GPT4 while using minimal storage and operating offline. By incorporating complex explanation traces, Orca enhances interpretability and addresses challenges in complex machine learning models. It outperforms other models in terms of accuracy, performance, and interpretability. The training process involves tokenization, sequencing, and loss computation. Experiments demonstrate Orca's proficiency in various tasks and domains, showcasing its capabilities in writing, comprehension, and reasoning. The research paper offers detailed insights and comparisons with GPT 3.5 and GPT-4, highlighting the potential of Orca to empower smaller models in competing with larger counterparts.
Not taking it personally.
I would also appreciate the ability to customize, but it would be helpful to begin with a curated list of instances for each topic.
Yeah, couldn't agree more.
Why don't you read the issue? It's in lemmy-ui, so it's clearly client-side. So just because you want to waste your time going through hundreds of instances to find similar communities, do we have to force everyone else to do the same?
I would prefer something pre-made for convenience but that can be modified by each user to adjust to their preference. I'd rather have a generalist solution forced on me than have to spend countless hours grouping communities from hundreds of instances.
There could be conflicts between hashtags, as a hashtag for one community may not have the same meaning for another community. This would result in mixing topics and potential confusion.
Oh, I thought it was about tagging the communities and merging them based on those tags. Are you suggesting tagging the posts instead, and displaying all posts tagged the same from all communities across all federated instances in the same location?
But this can already be accomplished with the search feature. You only need to select 'Local' or 'All' and search for a word. People shouldn't be forced to hashtag every post, so the result would be the same as it is now.
Over the past few days, I've witnessed a remarkable surge in the number of communities on browse.feddit.de. What started with 2k communities quickly grew to 4k, and now it has reached an astonishing 8k. While this exponential growth signifies a thriving platform, it also brings forth challenges such as increased fragmentation and the emergence of echo chambers. To tackle these issues, I propose the implementation of a Cross-Instance Automatic Multireddit feature within Lemmy. This feature aims to consolidate posts from communities with similar topics across all federated instances into a centralized location. By doing so, we can mitigate community fragmentation, counter the formation of echo chambers, and ultimately foster stronger community engagement. I welcome any insights or recommendations regarding the optimal implementation of this feature to ensure its effectiveness and success.