Not that I’m aware of. The Lemmy APIs provide access to that data but I don’t know of any existing tool that uses it for the purpose of exporting posts or comments.

All your old stuff will stay visible even after lemm.ee goes down, but it won’t be linked with whatever new user you create on another instance.

If export and import of posts and comments was possible it would result in “duplicating” your posts and comments to your new account, which as you might imagine would be an absolute mess (not to mention technically infeasible - how would comment chains with other users work?) so you can presumably understand why it isn’t.

It’s quite annoying for sure (and I’m a lemm.ee user too, so I’m also annoyed with everything I’m losing) but this is the trade-off we accept with federation that allows Lemmy as a whole to be robust and keep going even without lemm.ee

VSCode is by far and away the best thing Microsoft has ever done. (I’m sure therefore they will ruin it eventually, but that’s a separate issue)

Its good for two main reasons IMO:

1. It is plugin-based

2. It is (therefore) language-agnostic

Plugins mean the DE starts as a very lightweight thing that is basically nothing more than a text editor. You can then add as much or as little as you want to get the level of features you are comfortable with but without being too bloated.

And then, because it’s all plugins, you can work with any language and still stay within the same editor. Divine.

I personally love how lightweight it is compared to a full IDE because I don’t like it when IDEs hide the magic behind UI. Press the button and it compiles huh? But how? What’s going on there? What toolchain and commands are being executed?

I much prefer a good MAKEFILE where you know what your entry points are and what is going on, because it makes everything so much more portable and also improves your own knowledge and understanding.

Wireguard doesn’t necessarily need to have those limitations, but it will depend in part how your VPN profile is set up.

If you configured your wireguard profile to always route all traffic over the VPN then yeah, you won’t be able to access local networks. And maybe that’s what you want, in which case fine :)

But you can also set the profile to only route traffic that is destined for an address on the target network (I.e your home network) and the rest will route as normal.

This second type of routing only works properly however when there are no address conflicts between the network you are on (i.e. someone else’s WiFi) and your home network.

For this reason if you want to do this it’s best to avoid on your own home network the common ranges almost everyone uses as default, i.e. 192.168.0.* and 10.0.0.*

I reconfigured my home network to 192.168.22.* for that reason. Now I never hit conflicts and VPN can stay on all the time but only traversed when needed :)

And you can say no if you want to!