What I know so far:

  • vlemmy is still “up” and intermittently accessible. It is running slow as hell, PLEASE DO NOT VISIT THE INSTANCE as it will likely only slow things down more and make it inaccessible again.

  • Stripe, Librepay, and Github accounts are all closed. Closure date unknown
  • Reddit account still exists and has been messaged
  • No mentions of the instance in Element.io chats but still searching
  • They have almost certainly NOT lost their domain. Who.is historical records show no ownership or nameserver changes.

I have some minor personal details I’ve found that I’ll be deep driving on later, but it’s 1AM EST. I’m heading to bed but will continue on the investigation around 9AM EST.

Update 1PM EST July 9th:

Hi all, I’m working through about 40 different potential leads right now.

Although I need some help! Specifically, I need people who have viewed !kerbalspaceprogram@vlemmy.net to check their browser cache for this image:

https://vlemmy.net/pictrs/image/928b2f95-a37c-4e94-bd70-bc014c8655d4.jpeg

You can do so using one of the following NIrsoft tools:

I’m hoping since it’s a historic image linked to their internet presence that it might generate specific leads.

I’ll update more as things progress.

  • Atiran@lemm.eeEnglish
    15·
    1 year ago

    I think it’s natural that there should be a small collection of large, production-class instances that host the vast majority of users. The important point is that there are more than a few, and certainly more than one.

    I also think it is important for instance admins to lay out their plan for how they intend to host and fund an instance if they intend to be production-class.

    We also need some kind of account backup and migration tool so that if an instance goes down, those users can easily recover on another instance.

    • Coelacanth@feddit.nuEnglish
      8·
      1 year ago

      Account migration and/or linking across instances would be huge and I think has been requested on GitHub already. It already exists Mastodon so it should be possible, but since that service is follower-centric it’s a little easier there I would imagine. I’m not sure you migrate your whole post history, just your followers, I think.

      More production class instances to build redundancy would be ideal, and hopefully lemm.ee and lemmy.one can continue to grow and eventually exist as equal alternatives to lemmy.world.