Cool to see you back!

:(

I'm ready.

back to the meme mines with you

Feelsbadman, I feel like we were just starting to grow too :/

WHEW!

Man it sucked being stuck in that transporter buffer.

The slrpnk.net server went down and the admin wasn’t able to physically get to the server to fix the issue. It appears it came back up quicker than anticipated.

https://lemmy.dbzer0.com/post/45900905

there anything I can do to guard against that issue in the future? Is there a way to mirror an account between two instances or something?

Open an alt, export/import your settings

I have alts. No automatic sync, but you can list your alts in your profile like I do.

On mobile make sure to use a client which makes it easy to switch between accounts (I use Thunder, which additionally shows server status in the account switcher!)

It's possible to export your Subscriptions, Community/instance blocks, and saved posts/comments to an account on a different instance by exporting your account's JSON file, which you can do in your Account Settings page.

You can then import the JSON file in that same area on your alternative backup account, so that your experience is uninterrupted. Personally I would recommend making a backup account on Sopuli.xyz or Lemmy.cafe, they'll give you the most similar vibe due to how their instances are set up.

Tbh, the vast majority of performance issues don't come from the language but from the application itself.

While python is clearly slower than rust when it comes to pure native performance when doing exactly the same things exactly the same way and only within the language itself, the same isn't necessarily true in the bigger picture.

• Python uses C modules under the hood. A lot of the functions you call actually utilize C with C performance.
• Lower level languages allow the programmer to fail harder. While perfect low-level language code usually runs faster than perfect high-level language, the same cannot be necessarily said for bad or average code. For example, it's really hard to make an actual memory leak in Python. It's super easy to do so in languages without built-in memory management. The same applies in many other cases too. Python just gives you a lot of already-done tools that you only have to use, while other languages allow you to build the tools from scratch, which is easy to mess up.
• Most performance is lost due to using wrong algorithms or data structures. It's quite common when optimizing that you e.g. manage to eliminate a nested loop or something like that (e.g. loops hidden inside functions you call), and suddenly you improve performance by a factor of 1000. The same can't be done by switching languages, where even the most inefficient languages are only maybe 10x slower than the fastest languages.

So independent of the programming language, investing time in optimizing can improve the performance much more than using a faster language, and it's much easier to make perfectly optimized high-level language code than perfectly optimized low-level language code.

It is the medium term plan, yes (if feasible).

The user facing side of Piefed is more optimized for speed and low resource use, which fits well with our Solarpunk ethos, and on the backend side I expect it to be easier to maintain and the performance impact should be neglible as most of it is the Postgres database with Lemmy and likely Piefed as well.