It’s excruciatingly obnoxious to have to rely on third party sources for what should be a first-party feature.
Like, I select all and then search a query. “Oh no, nobody on your server used a third party service to find it, so you won’t see it here.”
Like, how short-sighted is that, really? If I search for a string in the ‘all’ servers, I should have a list of ‘all’ the servers containing that string.
It’s a really simple concept. Not sure why this post even has to be made, but I’m wondering if there’s something I can do to make these ‘features’ more intuitive.
What does ‘All’ mean to you?
In this context it means all posts which are stored on the server you are on. And only things are stored which people subscribed to. It does not mean “‘all’ servers”.
There are good reasons why the protocol has been designed like that, if you’re interested then you can find out about it. If not, reddit still exists for people who like it more.
All means all. If it isn’t actually All (it isn’t) then it should be called something else.
But it is all, just not the all you think, it’s all things the server is aware of, not all things in the universe.
This is not obvious to anyone who doesn’t have some understanding of how networking and federation work, which is most people. Especially if we’re talking about users who have only ever experienced centralized platforms.
It should be called “Known Network” or something more transparent that doesn’t require an explanation of indexing
I agree. But the attitude of those users just ribbs me the wrong way.
It’s an understandable response. They were previously in a position where this was such an obvious concept that it didn’t merit any thought, and now they are required to have an understanding of networking and federation in order to understand how well actually this a fundamental part of how distributed systems work and isn’t technically a bug.
From their perspective this seems like a fairly straightforward problem. Obviously (to us) it’s not, but the threshold for the fediverse shouldn’t be that you deeply understand federation if there’s ever going to be meaningful adoption.
As an aside, your personal domain is timing out.
Damn, thanks, I have a bad implementation of getting Twitter avatars and now that Twitter redirects everything which is not logged in my implementation goes into redirect hell every time someone opens a page with a Twitter comment. Perhaps I’ll find the time tonight to look for a fix.
It seems I was able to fix it by adding
curl.max_redirects = 3
to my caching code. No idea why it would hang without it because it gets the image from Twitter just fine now too.Uh… no it’s not.
I’m sorry, but what you’re doing is actively making this service harder to use by suggesting that ‘all’ should only mean ‘the communities other community members have subscribed to that contain that string.’
Where do the community members even find the the ones to subscribe to? Oh, they use a third-party service or ‘just know’ because… whatever reason.
Gee, fediverse design strikes again. Sorry, it has to be said. It really does.
The Internet also has all information made available to it, not all information that is in the universe. Same as the fediverse users, internet users rely on search engines to find what they are looking for.
When all would mean all available in fediverse you would get issues:
It’s to the user to search what he wants to see. I for one have 3 ‘main’ accounts (world, ml and studio) and I subscribe to specific communities for each account (ml for development, studio for music related, world for ‘rest’) and each one I open the feed with subscribed. I’m totally not interested in all, to much junk (even on Lemmy).
To freely quote: All, you want all? You can’t handle all. ;)
I cannot believe you’re making this argument.
I’m sorry, I can, and it’s a big reason why fediverse design has a lot of progress to make.
I can’t believe this reaction. You sound like you think CompuServ was internet and got replaced by Google. (or even didn’t now the time before Google)
I admit that it would be nice to have a list of all available communities when looking at the all list in the communities section. When federating with another node, don’t get everything, just the community list or the other node so people can subscribe when they want to. But it’s just a nice to have, not a huge issue worth stating that ‘a lot’ is needed.
There were (and still are) separate communities before digg and reddit, the latter got to big for their own good and now the federated solution has nodes with a few to a lot of communities. It’s a nice balance between the fragmented communities before the big corporation invasion and the colossal sites. Pick what you like and when you like the Reddit setup, they’re still alive. (although the content quality is dropping fast)
deleted by creator
🥱
Calm down buddy. Your analogy has no water and you’re clearly fueled by emotion.
Take a step back, breath some fresh air, then come back when you’re ready to discuss civilly. Right now you’ve said nothing of substance.
So All does not show posts from all instances federated with your instance, but only posts from all communities subscribed to by people in your instance?
Correct.
Source: On my one person instance All = Subscribed
The word “all” fundamentally means everything? By calling it “all” they are really doing a disservice to everyone who, gasp, assumes “all” means “all” when it really means “local communities and local user foreign subscriptions”. I don’t know what they should call it, but redefining the words “all” to be “not all” is super confusing, especially for users new to lemmy.
‘All’ to me means “”“all”“” the servers my instance can connect to that contain that string.
It’s a very simple concept.
Resource wise, it makes sense to only retrieve content the users of the instance are interested in. Think about all the nsfw communities popping on lemmynsfw and pornlemmy, as well as all the content in languages your users don’t speak.
Some instances are multilingual, so you don’t want to defederate from them (and defederation shouldn’t really be used in this context anyway), but retrieving 50% of content none of your users is ever going to read seems like a waste.
Yeah. And I’m interested in retrieving all of the servers my instance is connected to that contain a string in that community name.
Why is this so hard to get across to you?
Why don’t you have a solution for how server members find communities on different servers in the first place? Are you really defending relying on third-party services and ‘other means’ to find communities on different servers?
I think that’s really bad design and a testament to why the fediverse is inaccessible to the general public.
It’s just not very simple, quite the contrary, you would need to have a server park like reddit has it to store everuthing on every instance, the databases would be so big that you would need specialosts running just the database servers.
Oh yes, it really is.
The implementation may not be easy, but the concept is very simple.