It’s not a problem with LW but aussie.zone taking too long to respond to the data being pushed. There are instances on the US that fixed this by taking initiative and setting up a system that would active pull the data from LW to keep in sync.
Why would I?
Because you are the most invested in getting people out of LW, and because you don’t trust other people that set up topic-based instances?
diverse set of mods with good track record.
Why wouldn’t this be possible in a separate instance? Is the motivation to volunteer to mod in a community attached to the instance where it’s hosted?
It’s not a problem with LW but aussie.zone taking too long to respond to the data being pushed. There are instances on the US that fixed this by taking initiative and setting up a system that would active pull the data from LW to keep in sync.
Geographical distance between Europe and Australia is also at play.
Because you are the most invested in getting people out of LW, and because you don’t trust other people that set up topic-based instances?
I trust the admins of the topic-based instances hosting the following communities, so I’m not sure what you mean?
Geographical distance between Europe and Australia
Only because aussie.zone is relying exclusive on waiting the data to be pushed. If they pulled the data in bulk, latency would not be an issue and the problem would be immediately solved.
topic-based instances hosting the following communities
Aside from mander.xyz, the other instances are not topic-specific. They have communities which are focused of a more general scope, and its users are not focused on conversations around an exclusive topic.
Anyhow, the point is: as of yet, there is no one running an instance focused on Fediverse news and discussion. Wouldn’t it be nice if you, I don’t know, volunteered to do so?
Ah, sorry, I wasn’t complete above: I meant a diverse set of mods and admins
I am sure you can find people to help you co-admin the instance as well, if you set one up.
That isn’t how lemmy and the activitypub protocol work. Source instance pushes metadata about new content, remote instance then needs to pull it. If we’ve not received the push yet, we can’t pull the additional info.
I responded to you before I had my coffee, so I didn’t realize that you are one of the admins for aussie.zone.
I will tell you what: I am 100% sure that I can write a service that can work as a bulk message relay and I’m equally sure that I can modify Fediverser’s code to make it able to ingest data from the relay. If you want to join Lemmy’s Matrix Room, we can chat to see how to best solve this.
Note I said lemmy AND the activitypub protocol, ie lemmy does not currently have this capability. If it were added to mainline lemmy I’d be open to configuring it, but its not so I can’t.
The root cause of the issue is well understood, the solution is available in lemmy already: multiple concurrent outgoing federation connections to remote instances. AZ has had this configured since it was available. LW have not yet enabled this, though they’re now running a version that has it available.
Appreciate the offer, but I’m not interested in customising the AZ server configuration more than it already is. If you write it up and submit a PR that the main lemmy devs incorporate, I’d be happy to look at it.
I’m not interested in customising the AZ server configuration more than it already is
There would be no customization of Lemmy itself. You’d only have to add a sidecar service.
If you don’t want to do it, fine, no one can force you to. But then perhaps it would be nice to be transparent with your users and tell them that the delay in federation can be avoided.
You’re contradicting yourself there. By definition adding an external service is a customization to lemmy. I’m not interested in running un-vetted software from a third party.
This has been discussed previously with a request from a reputable source to batching content from LW. That setup required an additional server for AZ, close to LW. And for LW to send their outgoing federation traffic for AZ to it, which then batched and send to the real AZ server. This offer was declined, though appreciated.
I’ve been transparent and open about the situation. You seem to think this is the fault of AZ, and we’re willfully not taking an action that we should be taking. This is not the case.
As it stands the issue is inherent with single threaded lemmy federation, which is why the devs added the option for multiple concurrent threads. Until LW enable this feature, we’ll see delayed content from them when their activity volume is greater than what can be federated with a single thread. To imply this is the fault of the receiving instances is disingenuous at best, and deliberately misleading at worst.
You won’t be making any changes to Lemmy source code itself, that’s what I mean. I wouldn’t count adding something that is independent from the service as “customizing it”, but if that is what you meant, fine.
That setup required an additional server for AZ
What I had in mind would be to run the relay myself, and you would only have to set up/manage an extra service that could run along your Lemmy process.
You seem to think (…) we’re willfully not taking an action that we should be taking.
Well, yes? You have the possibility to take the initiative and mitigate an issue that is affecting your users, and you can solve the problem independently of the third-party’s cooperation. Why put yourself at the mercy of others when you have enough power and agency?
Only because aussie.zone is relying exclusive on waiting the data to be pushed. If they pulled the data in bulk, latency would not be an issue and the problem would be immediately solved.
Aside from mander.xyz, the other instances are not topic-specific. They have communities which are focused of a more general scope, and its users are not focused on conversations around an exclusive topic.
How are programming.dev and lemdro.id not topic specific? It’s in their names
Anyhow, the point is: as of yet, there is no one running an instance focused on Fediverse news and discussion. Wouldn’t it be nice if you, I don’t know, volunteered to do so?
You want to go back to the "is sysadmin more volunteering than community building ?
First, as the last post on https://metacritics.zone/ was seven days ago, wouldn’t it also be nice if you volunteered some of your time to keep your communities and instances active?
Second, I got another admin recently who told me that I should just stop discussing with you. Maybe I should.
I am sure you can find people to help you co-admin the instance as well, if you set one up.
As stated above, I’m as interested as sysadmining than you are in community building
lemdro.id also has communities like “Microsoft” and “ChatGPT”. “Linux” is only tangentially related to programming.
wouldn’t it also be nice if you volunteered some of your time to keep your communities and instances active
They are not “my” communities. I started the topic-specific instances as a way to help the general ecosystem and to have a destination for the alien.top posts. I was hoping that would help bootstrap more usage outside of the larger instances. I may post from time to time when I find anything interesting, but I do not hold any pretense to keep all 15+ instances and 200+ communities fresh with content all the time.
As stated above, I’m as interested as sysadmining than you are in community building
I am interested in the community building, I am just not committing to do it for hundreds of them on top of the work of running the instances and on top of developing tools in the ecosystem.
lemdro.id also has communities like “Microsoft” and “ChatGPT”. “Linux” is only tangentially related to programming.
Agree to disagree
I am interested in the community building, I am just not committing to do it for hundreds of them on top of the work of running the instances and on top of developing tools in the ecosystem.
I am interested in system administration, I just prefer not to commit to it on top of keeping dozens of communities active and promoting Lemmy and others on Reddit.
That’s what I meant previously: we both dedicate our time and energy to different activities about the platform.
What upsets me in this whole thing is that you present an impossible dilemma: if I run the instance, you won’t participate because you think it is associated with the money-making business. If I say “okay, then you go find an instance that is topic specific and and only for groups”, you find any possible reason to balk.
So here we are: you want to have someone that can focus on instance administration and you want to focus on building communities, but God forbid you even consider doing it a way that is only tangentially connected to a commercial venture. That is the part I don’t understand.
So here we are: you want to have someone that can focus on instance administration and you want to focus on building communities, but God forbid you even considering doing it a way that is only tangentially connected to a commercial venture. That is the part I don’t understand.
None of the admins of the instances above have stated that they are actively looking to make a business out of the platform.
It’s not a problem with LW but aussie.zone taking too long to respond to the data being pushed. There are instances on the US that fixed this by taking initiative and setting up a system that would active pull the data from LW to keep in sync.
Because you are the most invested in getting people out of LW, and because you don’t trust other people that set up topic-based instances?
Why wouldn’t this be possible in a separate instance? Is the motivation to volunteer to mod in a community attached to the instance where it’s hosted?
Geographical distance between Europe and Australia is also at play.
I trust the admins of the topic-based instances hosting the following communities, so I’m not sure what you mean?
Ah, sorry, I wasn’t complete above: I meant a diverse set of mods and admins
Only because aussie.zone is relying exclusive on waiting the data to be pushed. If they pulled the data in bulk, latency would not be an issue and the problem would be immediately solved.
Aside from mander.xyz, the other instances are not topic-specific. They have communities which are focused of a more general scope, and its users are not focused on conversations around an exclusive topic.
Anyhow, the point is: as of yet, there is no one running an instance focused on Fediverse news and discussion. Wouldn’t it be nice if you, I don’t know, volunteered to do so?
I am sure you can find people to help you co-admin the instance as well, if you set one up.
That isn’t how lemmy and the activitypub protocol work. Source instance pushes metadata about new content, remote instance then needs to pull it. If we’ve not received the push yet, we can’t pull the additional info.
There is absolutely nothing in the AP spec that prevents people from pulling data from the outboxes instead of waiting to be pushed.
I responded to you before I had my coffee, so I didn’t realize that you are one of the admins for aussie.zone.
I will tell you what: I am 100% sure that I can write a service that can work as a bulk message relay and I’m equally sure that I can modify Fediverser’s code to make it able to ingest data from the relay. If you want to join Lemmy’s Matrix Room, we can chat to see how to best solve this.
Note I said lemmy AND the activitypub protocol, ie lemmy does not currently have this capability. If it were added to mainline lemmy I’d be open to configuring it, but its not so I can’t.
The root cause of the issue is well understood, the solution is available in lemmy already: multiple concurrent outgoing federation connections to remote instances. AZ has had this configured since it was available. LW have not yet enabled this, though they’re now running a version that has it available.
Appreciate the offer, but I’m not interested in customising the AZ server configuration more than it already is. If you write it up and submit a PR that the main lemmy devs incorporate, I’d be happy to look at it.
There would be no customization of Lemmy itself. You’d only have to add a sidecar service.
If you don’t want to do it, fine, no one can force you to. But then perhaps it would be nice to be transparent with your users and tell them that the delay in federation can be avoided.
You’re contradicting yourself there. By definition adding an external service is a customization to lemmy. I’m not interested in running un-vetted software from a third party.
This has been discussed previously with a request from a reputable source to batching content from LW. That setup required an additional server for AZ, close to LW. And for LW to send their outgoing federation traffic for AZ to it, which then batched and send to the real AZ server. This offer was declined, though appreciated.
I’ve been transparent and open about the situation. You seem to think this is the fault of AZ, and we’re willfully not taking an action that we should be taking. This is not the case.
As it stands the issue is inherent with single threaded lemmy federation, which is why the devs added the option for multiple concurrent threads. Until LW enable this feature, we’ll see delayed content from them when their activity volume is greater than what can be federated with a single thread. To imply this is the fault of the receiving instances is disingenuous at best, and deliberately misleading at worst.
You won’t be making any changes to Lemmy source code itself, that’s what I mean. I wouldn’t count adding something that is independent from the service as “customizing it”, but if that is what you meant, fine.
What I had in mind would be to run the relay myself, and you would only have to set up/manage an extra service that could run along your Lemmy process.
Well, yes? You have the possibility to take the initiative and mitigate an issue that is affecting your users, and you can solve the problem independently of the third-party’s cooperation. Why put yourself at the mercy of others when you have enough power and agency?
Hello, @lodion@aussie.zone @Nath@aussie.zone was this an option you were aware of?
How are programming.dev and lemdro.id not topic specific? It’s in their names
You want to go back to the "is sysadmin more volunteering than community building ?
First, as the last post on https://metacritics.zone/ was seven days ago, wouldn’t it also be nice if you volunteered some of your time to keep your communities and instances active?
Second, I got another admin recently who told me that I should just stop discussing with you. Maybe I should.
As stated above, I’m as interested as sysadmining than you are in community building
lemdro.id also has communities like “Microsoft” and “ChatGPT”. “Linux” is only tangentially related to programming.
They are not “my” communities. I started the topic-specific instances as a way to help the general ecosystem and to have a destination for the alien.top posts. I was hoping that would help bootstrap more usage outside of the larger instances. I may post from time to time when I find anything interesting, but I do not hold any pretense to keep all 15+ instances and 200+ communities fresh with content all the time.
I am interested in the community building, I am just not committing to do it for hundreds of them on top of the work of running the instances and on top of developing tools in the ecosystem.
Agree to disagree
I am interested in system administration, I just prefer not to commit to it on top of keeping dozens of communities active and promoting Lemmy and others on Reddit.
That’s what I meant previously: we both dedicate our time and energy to different activities about the platform.
Yeah, right…
What upsets me in this whole thing is that you present an impossible dilemma: if I run the instance, you won’t participate because you think it is associated with the money-making business. If I say “okay, then you go find an instance that is topic specific and and only for groups”, you find any possible reason to balk.
So here we are: you want to have someone that can focus on instance administration and you want to focus on building communities, but God forbid you even consider doing it a way that is only tangentially connected to a commercial venture. That is the part I don’t understand.
None of the admins of the instances above have stated that they are actively looking to make a business out of the platform.
So? I never said I want to make money out of the instances.