• 11 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle



  • I’m experiencing similar things:

    • Posts made here not appearing on other federated instances
    • Posts made by other federated instances disappearing or never appearing in communities here

    I’ve checked with alt accounts created on lemm.ee and sh.itjust.works which are subscribed to the same communities.

    @ruud@lemmy.world Is there a federation issue?

    Edit: I think this is a problem with all communities on lemmy.ml. I’m new to the fediverse concept, but the issue seems to specifically be with them.





















  • This is helpful, thanks.

    It doesn’t cost you anything to sign up for, so give it a try.

    The main cost is time, to understand the platform and to find community. I created a Kbin account, but I don’t see myself having the time to be divided between Kbin and Lemmy so I’m hoping not to have to maintain both.

    Kbin federates with Lemmy - so users can engage in each other’s posts.

    This gives me hope. So is it basically just a different UI? This is where my understanding of the fediverse breaks down.


  • Can you elaborate?

    I read that Kbin defederated with Lemmy because it couldn’t initially handle the influx of new users migrating from Reddit, but that it has federated again.

    So is it a Lemmy instance, like Beehaw?

    I know that Kbin doesn’t use communities (“/c/”) but uses magazines (“/m/”) so I thought it was different.

    I also read that there was some new way to post to Lemmy from Mastadon, but I thought those were different, like Reddit and Twitter. But they both rely on something called “ActivityPub”?

    So is Kbin similar to Lemmy (by being Reddit-like), but distinct like Mastadon (which is Twitter-like)?

    I didn’t have a Twitter account, but was a heavy Reddit user. I don’t have a Mastadon account, but I’m liking Lemmy. However I have some FOMO about Kbin because I don’t understand how it all works together.




  • I made a slight modification to your bookmarklet asking to which instance you are migrating, which produces a list of links you can paste into something like https://www.openallurls.com so it becomes just a matter of clicking all of the “Subscribe” buttons:

    javascript:(function() {
      const currentHostname = window.location.hostname;
      const tld = prompt("Please enter the name of the instance to which you are migrating:");
      const table = document.getElementById('community_table');
      const anchorTags = table.getElementsByTagName('a');
      const communityUrls = [];
    
      for (let i = 0; i < anchorTags.length; i++) {
        const title = anchorTags[i].title.substring(1);
        const parts = title.split('@');
        const community = parts[0].trim();
        const domain = parts[1] ? parts[1].trim() : currentHostname;
        const communityUrl = `https://${tld}/c/${community}@${domain}`;
        communityUrls.push(communityUrl);
      }
    
      const urlsText = communityUrls.join('\n');
    
      navigator.clipboard.writeText(urlsText)
        .then(() => {
          alert('Community URLs copied to clipboard!');
        })
        .catch((error) => {
          alert('Failed to copy Community URLs to clipboard:', error);
        });
    })();