• 0 Posts
  • 37 Comments
Joined 2 years ago
cake
Cake day: April 24th, 2023

help-circle
  • To share from your home instance the post would need to be recreated on that instance, so a new community with the same name would need to be created with it.

    That is essentially what already happens, when you subscribe to a community from another instance, it creates a community on your instance with the same metadata (sidebar contents, icon, etc) and appends the @instance.tld suffix to the end of it. Your instance then sends a message to the original instance saying “Add me to your mailing list for posts/comments/votes/moderator actions for this community”. When you’re viewing comments and posts from a remote instance, you’re viewing the copy of it that your instance has (hence why post and comment IDs are not global - they are unique to your instance), its not fetched in real time.

    After one of those new actions gets added to the original community’s instance, it replicates that action to all instances that have at least one subscriber to the community. It also works in reverse, when you cast a vote, reply, etc your instance sends that action to the original one so that all (subscribed) instances have a copy of it.

    If I were to say, block all IPs on my server except for my own IP, I’d still be able to view this post because my instance’s database has a copy of it, I just wouldn’t receive anything new on it. This has been noted as a potential issue for deleting data and following various regulations, because if you were to delete this comment after I took my server offline (or changed Lemmy’s code to not honor deletions), I’d still be able to see your comment because my instance never got the signal that you deleted it - there is no way to guarantee deletion of content on the Fediverse for this reason.

    This is also why every now and then you get “vote drift” where the votes on comments and posts aren’t in sync, because the signal that a new vote was casted didn’t make it to your instance for some reason. Or if someone comments from an instance that yours is defederated from (but the original hosting instance isn’t defederated from) your instance won’t show those comments, but if you go to the original instance (or even the one from the instance that was defederated) it will show up.







  • I don’t think Sync itself is able to set the language filter, however I do know that on the website itself you can change what languages you wish to see - this should affect the API and thus apply to Sync and any other apps you’re signed into.

    It looks like you’re on lemmy.world so that should be over on this page under “Languages” - keep in mind the warning that it gives about deselecting the “Undetermined” option. If you deselect that option, a lot of posts/comments may end up getting hidden, since I believe Lemmy by default sends posts and comments as “Undetermined” unless you explicitly select otherwise (I don’t know if Sync itself sends it as - I assume its undetermined though). On desktop, you hold “Control” to select multiple items, and depending on your browser / device on mobile it should show a selection menu that allows you to check-mark the ones you want.







  • I can’t seem to find the source right now (so take this with a grain of salt), but someone did check the Lemmy codebase to look into this scenario - if an instance has downvotes disabled, it won’t propagate incoming downvotes.

    I know that on my instance which does have downvotes enabled, if I check out any post from Beehaw (who does have downvotes disabled) there are zero downvotes on any comments as far as I can see.

    Now I’m assuming this would only apply on communities hosted on that (or any downvote-disabled) instance, using my previous example if someone from Beehaw were to comment on a community originating lemmy.ml, I believe they could still have their comments downvoted since lemmy.ml would be “hosting” the comment, so to speak.








  • Especially if you were to use sleep mode on the PC - then depending on your setup you can combine that with Wake-on-LAN and then just use another app on your phone/streaming device to send the “magic packet” to initialize a wake up.

    I’m not familiar with Moonlight, but I’d imagine that would prevent it from asking for a pin again as well.