falcoignis@reddthat.com to Linux@lemmy.mlEnglish · 1 year agouhhh... what do I call the "subreddits"?message-squaremessage-square189fedilinkarrow-up1170arrow-down13file-text
arrow-up1167arrow-down1message-squareuhhh... what do I call the "subreddits"?falcoignis@reddthat.com to Linux@lemmy.mlEnglish · 1 year agomessage-square189fedilinkfile-text
minus-squareHeimchen@lemmy.mllinkfedilinkEnglisharrow-up7arrow-down1·1 year agoInstances also need better names.
minus-squareMasterBlaster@lemmy.worldlinkfedilinkEnglisharrow-up6·1 year agoWhy not “servers”? That’s all they are. They serve content.
minus-squareSpacePirate@lemmy.mllinkfedilinkEnglisharrow-up1·1 year agoBecause technically, one server can host multiple instances. Instances are containerized— literally an instance of lemmy.
minus-squareCommunist@beehaw.orglinkfedilinkEnglisharrow-up1·1 year agoIs there any practical reason to actually do that, though?
minus-squareCommunist@beehaw.orglinkfedilinkEnglisharrow-up1·1 year agoI’m sorry, I don’t really understand, what would be the advantage of this over hosting another community? Can you give me an example of this catering where the server would want different rules per instance? Sorry, i’m not trying to be rude I just genuinely don’t get it.
minus-squareCommunist@beehaw.orglinkfedilinkEnglisharrow-up1·1 year agoI understand now, thank you so much!
minus-squareCommunist@beehaw.orglinkfedilinkEnglisharrow-up4·1 year agoWhat would you call gmail vs hotmail?
minus-squareamiuhle@feddit.delinkfedilinkEnglisharrow-up3·1 year agoBut that’s a provider/customer relationship, on the fediverse it isn’t.
minus-squareunfazedbeaver@lemmy.onelinkfedilinkEnglisharrow-up3·edit-21 year agoAgree on a technical level, but in terms of the average netizen being able to visualize the relationship, “providers” makes it much easier
minus-squareamiuhle@feddit.delinkfedilinkEnglisharrow-up2·1 year agoI don’t think we should try to visualize something that’s not there just because it’s (supposedly) easier for the average netizen.
minus-squareFerk@lemmy.mllinkfedilinkEnglisharrow-up2·edit-21 year agoIt’s provider/consumer (not customer, something being a “provider” doesn’t necessarily mean they are selling stuff). We are consumers, we consume the content that the instances provide, as content providers.
minus-squareJustin@lemmy.jlh.namelinkfedilinkEnglisharrow-up2·1 year agoFor now. Every mature decentralized service calls them providers. Phone providers, ISPs, email providers, etc. I guess usenet just calls them “news servers”, though.
Instances also need better names.
Why not “servers”? That’s all they are. They serve content.
Because technically, one server can host multiple instances. Instances are containerized— literally an instance of lemmy.
Is there any practical reason to actually do that, though?
deleted by creator
I’m sorry, I don’t really understand, what would be the advantage of this over hosting another community?
Can you give me an example of this catering where the server would want different rules per instance?
Sorry, i’m not trying to be rude I just genuinely don’t get it.
deleted by creator
I understand now, thank you so much!
What would you call gmail vs hotmail?
Providers.
But that’s a provider/customer relationship, on the fediverse it isn’t.
Agree on a technical level, but in terms of the average netizen being able to visualize the relationship, “providers” makes it much easier
I don’t think we should try to visualize something that’s not there just because it’s (supposedly) easier for the average netizen.
It’s provider/consumer (not customer, something being a “provider” doesn’t necessarily mean they are selling stuff).
We are consumers, we consume the content that the instances provide, as content providers.
For now. Every mature decentralized service calls them providers. Phone providers, ISPs, email providers, etc. I guess usenet just calls them “news servers”, though.