It looks like there are instructions here about hosting your own flatpak instance: https://docs.flatpak.org/en/latest/hosting-a-repository.html

Another solution to this situation is to squash your changes in place so that your branch is just 1 commit, and then do the rebase against your master branch or equivalent.

Works great if you’re willing to lose the commit history on your branch, which obviously isn’t always the case.

Found a blog post that gives a quick overview of how to do git via email in general: https://peter.eisentraut.org/blog/2023/05/09/how-to-submit-a-patch-by-email-2023-edition

So at least from my understanding you’d make your changes, email the contents of the patch to the maintainer, and then they’d apply it on their side, do code review, email you comments, etc. until it was in an acceptable state.

There’s also the full kernel development wiki that goes into all the specifics: https://www.kernel.org/doc/html/v4.16/process/howto.html

(I never got through the whole thing)

I’ll also throw out: aging infrastructure, build systems, coding practices, etc.

I looked into contributing to the kernel - it’s already an uphill battle to understand such a large, complex piece of software written almost entirely in C - but then you also need to subscribe to busy mailing lists and contribute code via email, something I’ve never done at 30 and I’m betting most of the younger generation doesn’t even know is possible. I know it “works” but I’m really doubting it’s the most efficient way to be doing things in 2024 - there’s a reason so many infrastructure tools have been developed over the years.

The barriers to entry for a lot of projects is way too high, and IMO a lot of existing “grey” maintainers, somewhat understandably, have no interest in changing their processes after so much time. But if you make it too hard to contribute, no one will bother.

NPR News Now publishes great little 5 minute podcast digests every hour or 2 summarizing the big news items of the day / hour.

Their politics podcast and Trump’s Trials podcast are also good.

All three of these are very U.S. centric, obviously.

Simple thing, but are you sure you mounted the NFS share as NFSv4? I don’t have access to a machine to check right now, but I think it might default to mounting NFSv3, even if both sides support v4.

To add on to this answer (which is correct):

Your “of” can also just be a regular file if that’s easier to work with vs needing to create a new partition for the copy.

I’ll also say you might want to use the block size parameter “bs=” on “dd” to speed things up, especially if you are using fast storage. Using “dd” with “bs=1G” will speed things up tremendously if you have at least >1GB of RAM.

But on the other hand, if loans were subject to bankruptcy, most poor people would never be approved to get them.

I somehow read this as 128GB and was ready to share your shock.

Absolutely this. There are issues with deletes not federating properly too, right?

That’s a big part of the issue here too since even when .world cleans up the content it’s already been pushed out to every other instance and will now remain there until all THOSE admins also purge it.

Under this broad of a ruleset, all software would have to be open source.

The PR for the necessary back-end changes is out for review on GitHub: https://github.com/LemmyNet/lemmy/pull/3869

Maybe I’m completely misremembering things, but at some point wasn’t there a hotfix to Lemmy that hard-limited how many comments a thread could have? Does anyone know if there’s a maximum and if so how many?

Just wondering, cause uh, I could see this one having a lot of comments.

This one got me too.

lemmy.ml specifically is running requests through a user agent checker - and if it’s empty, which reqwest is by default, you will get a 403.

You can see an example here of using ClientBuilder to set a user agent string: https://github.com/CMahaff/lasim/blob/main/src/lemmy/api.rs

So set any string (should be your project name) and then it should work.

Author of the tool here! If you are okay letting me know the instance, I can definitely take a look and see if I can figure out the issue. I might need to make an account though.

There’s lots of Lemmy instances, and I’m always finding new quirks with different configs. But it’ll help the next person who might run into the same thing!

Author here! I’ve been posting about it a good bit, and especially with the hack of .world and vlemmy’s disappearance, now others have started sharing it too. Besides myself testing it with lemmy.ml, lemmy.world, and lemm.ee, I’ve seen at least a handful of people that say they’ve run it without issues. I’m assuming the real number is much higher but there isn’t any tracking in the app, or even a download counter, so I really have no idea.

Only known issue at the minute is whether it works on Mac OS X. It theoretically does, but the only person who attempted it ran into issues where OS X wanted to open it as a text file instead of running the program - and it’s the only platform I can’t test myself.

Obviously if you do have any issues you can report them on GitHub.

Apparently not per the post-hack report: https://lemmy.ml/post/1901079

LASIM definitely does not - it’s designed for desktop and written rust, so not easily portable to iOS/Android.

Doesn’t look like lemmy-migrate would either - it’s a python script - unless there’s a mobile python interpreter app or something.

Hey, author of LASIM here if people have any questions!

Just so people know it does save everything to a JSON file when you click “download” so you can absolutely upload to multiple accounts or keep it as a backup.

FYI there was a federation issue and long story short this post is effectively only visible to .world, while everyone else sees this one: https://lemmy.ml/post/1870958

Apologies!