|22 Jun 2021|
|Pirate Bady||being an arch user i find that offensive! 🙈||13:42:14|
|Madhav V⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ (Telegram)||Kittiyal pulikkuo 😝||13:42:40|
|Pirate Bady||no, but wouldn't be there better things to wish for? :D||13:47:25|
In reply to @telegram_293342249:tchncs.deWhat problems? Also that doesn't sound like 'quality of life' problem. That sounds more like band-aid for masochism problem.
|Madhav V⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ (Telegram)||Lol||13:55:09|
|goku12|| I recently learned that you have to check for ||13:59:23|
|goku12||Arch is a high maintenance system, requiring a lot of care from the user. It pays off significantly in other ways though - and those are the benefits users stay on for. Arch wiki has an entire wiki page dedicated to system maintenance that all arch users must know and follow regularly and religiously, to keep their system clean and operational.||14:07:43|
|Pirate Bady||haven't heard about that, let me check.||14:09:21|
|goku12||* Arch is a high maintenance system, requiring a lot of care from the user. It pays off significantly in other ways though - and those are the benefits users stay on for. Arch wiki has an entire wiki page dedicated to system maintenance that all arch users must know and follow regularly and religiously, to keep their system clean and operational.||14:10:15|
|Pirate Bady||https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave thanks 👍️||14:10:18|
|Madhav V⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ (Telegram)|| |
In reply to @gokuldas:matrix.orgOk a system maintenance is long overdue
|Navaneeth (Telegram)||I have a small open source queue management website that I build and put it on GitHub under GPL3. Someone reached out to me asking if they can use it. Just keeping the GPL3 LICENSE as a file in the root folder and telling him to use it as they want, should do? I am not a license expert||18:03:19|
In reply to @telegram_345769011:tchncs.de
There are a few conditions for derivative works of GPL code. Most important are the following:
|Navaneeth (Telegram)||Do I have to go through some legal stuff to register the copyright?||18:21:57|
|Navaneeth (Telegram)||I am lazy, don’t think this is important enough to do that. Is that fine?||18:23:12|
|Navaneeth (Telegram)||This-> the project||18:23:29|
|goku12|| No. All creative works are copyrighted IP of the author by default. Copyright statements like ||18:24:05|
In reply to @telegram_345769011:tchncs.de* No. All creative works are copyrighted IP of the author by default. Copyright statements like
In reply to @telegram_345769011:tchncs.deDo what?
|Navaneeth (Telegram)|| |
In reply to @gokuldas:matrix.orgRegister a copyright
|Navaneeth (Telegram)||Curious to know, how do I prove that I am the author? Because code was pushed from my GitHub account?||18:26:22|
In reply to @telegram_345769011:tchncs.deThere is no legal registration step. You automatically and legally own the copyright when you create the work.
In reply to @telegram_345769011:tchncs.deThe work is assumed to be yours when you claim copyright. But anybody can dispute it if they have proof of claim. If you really foresee such a legal complication (sometimes people do maliciously and wrongly claim ownership), you can sign your work. Publishing on Github is acceptable, but cryptographic signing (using gnupg) is considered even stronger legally.
|Navaneeth (Telegram)||Ok. Just asked for understanding. Thanks||18:31:16|
In reply to @telegram_345769011:tchncs.deYou're welcome!
|Madhav V⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ (Telegram)||What exactly is "signing". How does that work for sourcecode||18:47:34|
In reply to @telegram_293342249:tchncs.de
'Signing' means an action that proves that you are the owner of certain data or document. Digital signing (or eSign) is done using cryptographic signing software, like Gnupg, minisign or X.509 PKI.
If you have a gpg keypair (which is your identity), you can sign a document using command
The same can be done for git commits. When you sign your git commits, it's a proof that the commits and its contents came from you. This can be done with command
Madhav V⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ (Telegram): If you really want to know how digital signing works, here is a somewhat simplistic and slightly inaccurate explanation.
The first step in signing is to take the 'cryptographic hash' of the plain-text data. The hash is small piece of data that is derived from the plain-text data and is unique. No other plaintext data gives the same hash (in theory). Also the hash can't be reversed (the plain-text data cannot be extracted from the hash).
The next step is to encrypt the hash using your 'private key'. Your private key is your secret, but your 'public key' is with everyone. Whatever is encrypted with the private key can be decrypted using the public key. The encrypted hash is called the signature.
So, if a signature can be decrypted with your public key, it means that you made the signature (because only you have the private key). And if the decrypted hash matches the plain-text data, then it's proof that you had the plain-text data with you.
|23 Jun 2021|
|merothh joined the room.||04:03:02|