• 2 Posts
  • 40 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle

  • hemmes@lemmy.onetoDad Jokes@lemmy.worldElectrician couple
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    1 year ago

    So there’s a couple of thoughts here, and I’ve only experimented a little bit.

    You can post directly from your Mastodon account to a community by calling out the community by its address like @[email protected] in your post (toot) (don’t think anything will happen by me using it here). You’ll see the Mastodon post as a community style post in the community like this: https://lemmy.world/post/1222638

    You can my click my mas.to profile and see some things in the Lemmy context - not my verified links, but things like my profile picture and background, bio, Cake day, sending me a message.

    I don’t know how to interact with Mastodon users viaa Lemmy or Kbin. Like above if I reference my Mastodon user @[email protected] I don’t believe anything happens.

    So OP’s only options are posting a snapshot or, my choice, he can add the Mastodon post link to his Lemmy community post (in the header not the body) and have the same results as any other web link - the Mastodon media would get a thumbnail in the community post listing, with maybe some relevant content preview, etc. While that will deliver a superior viewing experience, that’s not actually communicating with ActivityPub through the Fediverse, it’s simply a web link to the Mastodon instance server’s user’s post.

    Edit: Okay, so it looks like mentioning my mas.to handle does indeed alert me (almost instantly in this case), that’s cool!

    The post above yours is the main OP all laid out in Mastodon style. This is actually really cool.








  • Out of nowhere the instance went down. I believe it was late Saturday morning or so? It was my main instance and nobody has heard from the admin. He was always very enthusiastic and transparent, actively looking for more admins.

    A day or so before it went down, he made a post about having to defederate with another instance due to current violation laws in his server’s country of origin. VLemmy is known for not banning many (if any) instances in favor of moderation, so they take defederation very seriously.

    It looks like he got caught up with some bad content and had to shutdown. Not sure how long but all his tip and donation links have been closed including I believe his GitHub.






  • Well, that would be shitty.

    Not gonna go there at this point though. Like I said, he was a good admin up to this point. Just scary there’s complete radio silence. Like, what the heck happened lol.

    I really liked that instance. I like my .one instance. But I don’t mind re-subbing etc. I just want access to the fediverse and prefer solid, but smaller instances, with blocking as a last resort. I’ll be the first to say, I want my downvote button, I’m the type of user that likes to see and compare karma, but none of that matters to the point where all is lost if I have to setup a new user. I’m also the type of user that formats my hard drive once a year to start fresh lol.


  • Yeah, this is the strange part for me. Pyarra was a very transparent, active admin. I’m sure all he had to do was shut it down, make one post a direct message to admins and one of the other mainstreams would’ve picked it up - hell I would’ve migrated it to my setup in NY if no one else would answer the call.

    My point is - say anything, we’re all here to help.




  • Oh that’s from him?? Then yeah that’s what this seems like. But that’s exactly what I would do if illegal and risky shit ended up on my server. But I would post to another instance, Mastodon, or something to let users know what’s going on.

    (feel bad I forgot his name and obviously can’t check now, he appears to be a great admin)



  • Yeah, saw this one. Could be many reasons it’s parked. Could’ve been doing maintenance, migration, missed a renewal, etc. Doesn’t mean it’s gone. Any DNS updates may be subject to TTLs as long as an hour or more (not usually but you never know), and that’s from whenever the update to DNS has been committed by the name servers, and then actually begins to propagate to other servers.