I'm a bit confused about where threads are coming from, it's hard to see if it's local or federated.
I'm a bit confused about where threads are coming from, it's hard to see if it's local or federated.
Take this post, for instance:
https://fedia.io/m/[email protected]/t/6403/Does-lemmy-world-allow-criticism-of-the-CCP
The user and magazine are both from Lemmy.world, but next to the title it says (fedia.io). What does that site in the parentheses mean?
So much new vocabulary for us noobs to learn. Interesting and entertaining
The post you linked is from the [email protected] community/magazine. This means that it's hosted on lemmy.world website. The url you gave is fedia.io, meaning that you're on fedia.io website, viewing a post hosted on lemmy.world.
I'm not really sure what the parenthesis listing is for.
I believe the parenthetical is where that particular link is hosted. So while the main post is on lemmy.world, that particular link will take you to the version of that thread that was pulled to fedia.io, which you see in the full link OP posted, it starts with "https://fedia.io," exactly as you pointed out. It makes sense for typical links like if you post an article from "nytimes.com" but is fairly confusing when it comes to federated content. I could be wrong, but that's what it looks like to me.
I have nothing to contribute except that it is so exciting to be right at the start of something.
Thanks for asking this. I was wondering the same thing.
I used Slide app for reddit which has the same design. It's not about federation, but the function as a link aggregator. For posts that contain a link, it's the link's domain. This post doesn't cotain a link, so it's "local" in that sense.
However it could become really confusing when federation is considered. If someone blocked the instance's domain, the post won't show up besides it's supposedly from fedia.io.
Maybe it's better to use Hacker News' approach: hide the domain if it's fedia.io. Show the domain related to federation in magazine name.
Ok that makes sense. Basically like "self" on reddit, which was also a bit confusing. It should probably say "article" or the instance it came from as you suggest.
Not sure how well federating is working at this time. For instance, if you search here (Fedia) for "RedditMigration" T. Chambers magazine on kbin.social. It finds it, but if you click on it, it is empty. You can then go to the "original" kbin.social profile, but you are not logged in. It seems that the local version is not federating well. Any ideas or thoughts? Is this just early days growing problems?
I understand that federation with kbin.social specifically is not working correctly but I’m seeing similar things with other instances also from here. Lemmy.ca as one example. Way more posts there than what shows up here in the magazines I’m subscribed to.
Between lemmy.world and fedia.io, magazines I'm viewing are at least 1 day behind the source. I figured it was due to the increase in new posts and the creation of additional lemmy instances that all have to sync.
Surprised no one has linked this Tampermonkey script that was just posted to Fedia: post.
Among other things it adds "@domain.com" to any links that don't have them. It maybe doesn't directly address the confusion, but it should help :)
the kbin.social instance shows the instance name that the post comes from. it also has a lot of various lemmy and kbin instances posts on the home page. It seems the front page here is more things posted directly to this instance. However, there have been server changes which might have messed up the federation syncing.
Just go to the kbin.social page and you'll see the difference
I believe that means you are accessing it via the Fediverse. Rather than directly on their site.
I'm putting together a little userscript to make some changes, including adding the domain to the magazine name. Any other ideas for small UI changes that could be done by a userscript?
Would collapsing a thread be too much for a userscript?
Good luck btw!
I've noticed this as well. It would be nice if the magazine name included the instance, e.g. [email protected] - since the content source (what's in the parentheses) is sometimes an external site.
Seems like you can look at the link to the post that should have an "@instancenamehere.com". So far that's how I've been checking post origination, but it'd be nice to have that built into the UI.