It was written as part of my work.

check your contract, you might not own the code and your organization may have a process to determine how to license something.

to your other questions (IANAL)

1. prior work wont be licensed, meaning no one but the owner of the work is allowed to do anything with versions prior to the license
2. you don’t have to, but i can’t see a reason why you should not.
3. GPL might mean that other work depending on gpl licensed code has to be licensed in a gpl compatible way, depending on how exactly you depend on it and how you distribute your dependencies. MIT/BSD is easier here, if you don’t plan to license everything with the GPL anyway.

no, the solution is not to pay someone to have someone to blame if shit happens.

there are a bus load of people involved on the way from a git repo to actuall stuff running on a machine and everyone in that chain is responsible to have an eye on what stuff they are building/packaging/installing/running and if something seems off, it’s their responsibility to investigate and communicate with each other.

attacks like this will not be solved by paying someone to read source code, because the code in the repo might not be what is going to run on a machine or might look absolutely fine in a vacuum or will be altered by some other part in the chain. and even if you have dedicated code readers, you cant be sure that they are not compromised or that their findings will reach the people running/packaging/depending on the software.

i can’t see how paying someone would have changed anything in this scenario.

this seems to be a long running campaign to get someone into a position where they could introduce malicious code. the only thing different would have been that the bad actor would have been paid by someone.

this is not to say, that people working on foss should not be paid. if anything we need more people actively reviewing code and release artifacts even if they are not a contributor or maintainer of a piece of software.

And no, I have not tested it because I don’t know how I’m actually supposed to do that.

depends on what you backup and how.

if it’s just “dumb” files (videos, music pictures etc.), just retrieve them from your backups and check if you can open the files.

complex stuff? probably try to rebuild the complex stuff from a backup and check if it works as expected and is in the state you expect it to be in. how to do that really depends on the complex stuff.

i’d guess for most people it’s enough to make sure to backup dumb files and configurations, so they can rebuild their stuff rather than being able to restore a complex system in exactly the same state it was in before bad things happened.

Fyi: Libre Office is the actively developed Open Office fork.

Don’t know how it stacks up to MS Office though.

Most clients are web browsers and support for torrents in http is the same as for every other file.

So that would only give us a use for torrents as a form of content distribution plattform to get the actual files closer to the client.

In cases where we have actual non browser clients: i like to curate what i am distributing and don’t want to distribute anything i happen stumble upon or would you be willing to store and more importantly share everything you find on 4chan or that might show up in your mastodon feed?

Maybe it hurds in a good way.

Nah, it’s a kernel it does kernel stuff and does not offer anything a normal user notices compared to other kernels.

It might be interesting for people who work on kernels just to see different ways on how to solve common problems.

I guess the biggest difference for users is that nostr relays don’t federate with one another. So you’ll have to query multiple relays yourself if you want to see stuff outside of the relay(s) you post to. The other big difference is that your identity is a keypair. The relays you send to only know your public key and that’s it.

E: someone running a relay could still decide you need to create an account or something, but this account is only the permission to use this specific relay. Your identity would still be your keypair, so moving to another relay is easy.

Eh, if i wanted to i could scrape various instances and do whatever i want. The question is would i be able to pin information to identities without the accompanying meta data or would i only get a big text corpus.

The benefit of the fediverse is that no instance can sell the whole package, because most instances only have the posts of most users and nothing more. Reddit has way more additional data that can be used to track and identify someone.

No, the right to be forgotten is about data that can be used to identify you stored by a service provider. It’s not a right to have every record on the internet purged.

I guess you could force Instances one by one to forget you, but a single provider only has to make sure they deleted the data they stored.