Instances can go down, disappear or be unresponsive due to many reasons.

Go to your account settings now and export your account settings!

This file contains your subscriptions, follows, profile settings etc. It's very easy to start over on a new instance when you have your export file.

Back it up, export it, save it, repeat occasionally.

all 23 comments

sorted by: hot top controversial new old
[–] 42 points 6 months ago (2 children)

Or you know, just embrace impermanence.

  • source
  • hideshow 2 child comments
  • [–] 10 points 6 months ago (2 children)

    you guys get too serious about social media. just let the whole thing burn. youll register another temp email the next day and browse the same 3 active subs.

  • source
  • hideshow 2 child comments
  • [–] 4 points 6 months ago

    Great idea, one of those retrospectively obvious ideas that never occurred to me!

  • source
  • [–] 3 points 6 months ago

    @general@lemmy.worldThis file contains your subscriptions, follows, profile settings etc.Just an addendum so Fediverse newcomers don't assume things from your "etc.": , at least not without republishing, IIRC. There are Fediverse platforms that allows for "importing" these from an old account (the platform I use, a Misskey fork, has this feature), but all it does is republishing anew, as neither authorship nor timestamp from old activities are reassignable, as per ActivityPub standards. To complicate things, republishing isn't something nice to do when the person has a history comprised of thousands of activities, including replies/threads where handles for Lemmy communities are mentioned (so I guess each post would end up as new, repeated threads/replies across the threadiverse).I say this because I'm currently facing this exact conundrum myself: for almost a year, I've had a Calckey account (@dsilverz@calckey.world) from which I've posted a thousand notes, (mostly) including interactions with Lemmy and hundreds of microblogging, but then the instance I was housed in started getting some issues beyond the scope of this reply (rule 5). I saw myself in need of seeking another instance, one that uses the same platform (because I liked Misskey, its features and how it allows for having both threadiverse communities alongside a personal feed), and I found the nice Catodon instance I'm currently housed in.I was able to easily customize my new account's settings with the same settings that of my earlier account (because both platforms share the same Misskey origins), including the vampe UI theme I use, but the only thing I can practically do regarding my thousand posts is exporting these as a JSON and redownloading their media in some kind of post-mortem archive, because even republishing my microblogging posts would be unfeasible (I mean, technically speaking I , it doesn't mean I , because it'd end up as a flood of posts, so I'm not doing it).

  • source
  • [–] 2 points 6 months ago (3 children)

    Is there a way to do this in Voyager?

  • source
  • hideshow 3 child comments
  • [–] 2 points 6 months ago (10 children)

    This simply needs to automatically happen every week or so.

  • source
  • hideshow 10 child comments
  • [–] 7 points 6 months ago (8 children)

    How though? A website cannot just access your hard drive and write stuff, as far as I know.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 1 point 6 months ago

    There’s a file api you can use to interact with the file system directly. Practically, I’m not sure how much it would help, since you could only access it with permission while the website is open, and there’s no way to sync between devices, but it is hypothetically possible to write a feature that backs up your settings periodically.

  • source
  • parent
  • [–] -1 points 6 months ago (2 children)

    Wait, doesn't every website do this? Or are there websites that only live in RAM?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 6 months ago* (1 child)

    No websites should be able to access anything on your hard drive arbitrarily.

    Websites can ask the browser to store something in cookies, or local db storage; it can even say “here’s a file for download”. But it cannot just decide to place a download somewhere in your filesystem.

    The browser itself is accessing your filesystem to read and write cookies, cache, etc. and the website has (rightfully so) zero control over that, other than asking permission and offering up a link to something the browser may to may not decide what to do with.

  • source
  • parent
  • hideshow 1 child comment