I’d like the name to be “community feed” and “feeds” for short. Reddit was always essentially a collective rss with voting weights. In this way “subs” would still work since one subscribes to the feeds.
Ultimately it’s something the devs need to encourage though
Insurance companies will love the new discrimination machine, best not think about how it handles edge cases /s
This sort of AI use should be banned outside of a research context.
I agree, but it takes less than 10 min and is more impactful than lemmy posts
FWIW getting one of those disc suitcases can hold hundreds of dvds without taking up much space at all. If you rip backups, you can store it somewhere out of the way without too much clutter. Plus it’s a very stable backup for the digital files.
The thing is, meta has a user base 100sx the size of the fediverse, and absolutely no incentive to EEE a project that is very very niche and inaccessible to a lay audience.
I’m not sure blocking Meta is worthwhile in the long term. Say what you will about email, you still have some degree of choice over your host. I want better for the fediverse, but that’s still a marked improvement over mainstream social media.
In the short term, Meta wants to kill Twitter by collecting all its A-level users. I think this would be good for the fediverse, these are news outlets and poltiicians and etc making posts most people want the option to see in their feed. These are also users who want no-fuss platforms with some amount of “customer service”, and mastodon.social is simply not ready to provide that.
The issues it poses to re-centralization are an inevitable threat as the Fediverse grows. Unless there is a concrete plan to build protections and this is a stop-gap effort, I’m not yet convinced it’s worthwhile.
It’s really an issue with how the fediverse handles communities. On Reddit each sub had its own moderation/governance structure which I think fits the role of an “instance” best. Here, each instance has a variety of communities which may overlap with other instance.
I.e. banning an instance for having community X impacts community Z who may also dislike X.
Without ripping up the floorboards, I suspect the answer is instances having community-level granularity in blocking. So one can block: The_Donald@*, *@sh.itjust.works, or most narrowly [email protected]
I know I’m not alone here, but truly a Letterboxd version of bookwyrm would be amazing. Esp if it had some integrations with Jellyfin.
It’s not that straightforward. Copyright is different in that infringement is only enforced by rightsholders through litigation. That means they hato find you, sue you, and make a convincing argument that your backup is harming their market viability.
On that last point, some personal backup is unlikely to be found to be infringing. It’s more problematic if it’s something shared or done in a significant scale.