Kalcifer @ Kalcifer @lemm.ee

All of this user's content is licensed under CC BY 4.0

---

Read more

Posts

9

Comments

209

Joined

2 yr. ago

I don't understand your point. Are stating that if the victim didn't have a gun -- meaning that the shooting didn't happen -- then the perpetrator wouldn't be continuing this behaviour?

    
content-signature:ZXco0T3+z6ff9K0rbQCt+9w2lDEe4GHy9QuxOgIiJqKWfcGoazURsZea+8i/5DrTIHihOUN4GEY9HlHfzoEQCGLqZaby4yj+t0yUbP08HVgwPi1mV19bbieDKMJeXhNkpDwgqjc8rDcnyMgaPhlAY/W+nS6xWgIcrTMrf9H5LbhtZqIwHvo4kFgUz87mrt21L8rlOpvbiodZrrLx/1mHGXd3cdJJP92W1Z3x7t4E7NjKgstCnyCXtILMpejJkQH4cEPv1pdlHRQdjOrG32ZmyFWWn+LruZW+Xj4Vx5ueu87UupLpCPbTD5FWMGX/HTfBxR5XQs0oRYO8Eh1q8WY2Tg==

  

In every normal country this couldn’t happen because that guy wouldn’t have a gun in the first place.

Are you referring to a shooting in self-defence by a law-abiding gun owner? If so, then yes, if said law-abiding citizen didn't have a gun, then, by modus tollens, they wouldn't be able to use a gun in self-defence.

It would have ended in a fight or in the shooter suing the prankster and getting a lot of money while the prankster would be told by court to stop this stupid pranks.

You state "ended in a fight" as if that implies that the total damage imparted on both parties would be less overall. You completely miss the fact that physical violence can quite easily end fatally.

At any rate, wouldn't a victim defending themself successfully, efficiently, and likely without bodily harm to themself be preferential to the possibility of a violent and bloody physical beating with odds likely not in the victim's favor?

    
content-signature:BQVt7fAQqGvqjdNGUrvFp8iqrLRo8CmbObtXC5hFcYjFf60yg37xh7iyO8+vL4e2+pB5orcuBTuGgk1LMwFlyoDWKLb72FTczTCpRCwI6RoqF6YS1EOOli37Bi2Sod2Za/kjTaP6gijyrKUshxlhXQuiKPDkhGzpVtdKwgLlyziqBJzo3WQ0rIHKh/WWC0fmO6GQySYJQd6KVgDmrhzvIg0JXT7OpPPYM5QjnA+J14PXCqawJPmxmHbOF53MoV8QH8jszAt+ywzdRxI5eeM9aKifkX2+P8MUswT23ql95BEeG1egRAraue4yJ3OjaqeMUNFOPdDTGTguVSDjO1gctg==

  

I'm not trying to make a strawman argument with this comment, I would simply like to state the misfortune that some countries prohibit the use of pepper spray for self-defence. Canada is one such example that is known to me.

    
tshLz68OTxAkqdrN0fsu2PS0B3WTZAEQxH9bUUpQeu0M/piF3foJbme1ziay5+3XkCIyRUqO6fornlpkXdp0QK9/xIIy7Z/vf+NOSZ/NC+hrZsvmplMjNkhRJ3U2kzKEMINpt6NDvnsNrxsHMVO+V/wJLsA2a7sV/WZcrtHaxQmk+n6dATEK1NzGx5Dcl96wsiSTHLI7Y5cXtp7VvzZ4xQ6Vefg1CDf44lQnQcKUWcdY9DeTCksEUzQba0ee/UCO1HaoPhzlYnH4wNLayMOZHjg+l5uRSDFeEzEK8+ElNAQaP9rCG/g/RpvuPrwAkM2I6cCCQkudj1FdGEPSgSzYmQ==

  

Correct, people shouldn't go around shooting people that they don't like, but that isn't what happened here -- Alan Colie was acting in self-defence. That is, of course, unless you are of the opinion that people shouldn't be allowed to use firearms in self-defence.

    
bUDnRZ0kjJqfm8GENhao9dovO6CydCHTMb8Fz1TYwUic8xy6bD8bTg6VkagwSSwVhltuqEdYkZnT/02TOcKdOJ9VKvL//3scGs/TlSSPZ8LU1SvaoYyb/czu4qi25f6hTh2S8iMkQ7e3bbvlKvnACnsFMZL3afsWICGwXXSZxk5VodS18XZ1m3fUJLxdjMju+M2U0WuXyMVNCP7LI2wQI2gs2SH/LoFZPQLiRvsv6o6ryQyWIp2MlBWbT9oj/wAycuWmPnn3oFTt3xUm7LdSX8kFEArCy44Zv0zyNn1Utyt7AX+KJT3XWgdqTDuC4cBIHOOUhuEzOOoQ89iXs312kA==

  

Hm, one must be careful with such lines of thinking. Self-defense should be protected, and upheld based on principle, and not simply because it was used against someone who may socially detestable.

    
content-signature:Xpto6+CqmztueG93Hr9TWGrFEqsQlphBb5H+B7FKMK9J3SkSqbVdldBh2LPdJCBavk0ovU7/YXTEpWdkHnDRS/suKAKmDKrta0TpDY3CeF7S1iemSZ46Y4xa/texFQluvZ+OC6l6nGrYMoWRLeed/u7hgkD9DRafFiAmgP5uBxQeSAo2lKBQN5usXBJRU/80u7smOdbBj2t6HS/wRu4vkDYXmGpLqjPQvHAxcBvGR+4bDvQ28Df7Qnpea7NkK+gDBHKSMEW58WfdbQZihrwc/1oBGfbPXp2oR9rfPn3at3Ab/67PoyebHxJxvc7Ap7CAJveaSxfL0QCC9wepxo02jQ==

  

I certainly could link my server into play as well just to keep an always online device in the mix

Yep! That should work perfectly fine.

What is this post signature [...] Also, what is the purpose?

I'm testing out some ideas that I've had for my posts -- the signature and the edit history. They are a result of the current status of the following two issues on GitHub:

• Add the ability to view an edit history for posts
• Sign a user's posts and comments with a private key that only the user possesses, so that server admins are unable to secretly modify a user's content

Recently (as of 2023-10-02T03:28Z), one of the maintainers/developers for Lemmy closed those two issues with either little, or no rationale. I personally think that they are good features. Since it appears that those features are not going to be seamlessly added to Lemmy, I'm trying to see if it is practical to manually add them to posts.

Regarding the edit history: The purpose of an edit history is to solve the issue of people not knowing what changed in a post when it was edited. The main issue with a user-created, and maintained edit history, however, is its inherent the lack of trust. Its existence increases transparency, but you still have to trust that the user hasn't lied about what is in the diff. The implementation would be to have the server generate it, but, unfortunately, the dev has removed that possibility for the time being.

Regarding the signature: The purpose of the signature was a means to ensure censorship resilience from the admins of an instance. As it currently stands, any admin can freely edit the content of a user's posts, or comments with no one being the wiser. A signature would provide a sort of check against this. If a user signs a post with their own private key, then, by verifying the post's signature with the user's public key, one can be certain that that user was the one that wrote it, and not a server admin, or any other external entity. But, again, this feature has been blocked on GitHub.

The long, and short of it is this is me trying to protest what I think are silly decisions made by the devs of Lemmy.

how does one use it and create one for their own post?

The way that I am currently doing it is I take the raw content of the post, or comment (the body, and it's formatting, including the edits, if they exist, and excluding the signature code block), generate a SHA-256 hash of it, and sign the hash using RSA-2048. For example to sign one's post's content, the following could be done:

1. Put the raw post content into a file, post-content.txt.
2. Generate an RSA-2048 private key, and output it to a file, private-key.pem:

    
openssl genrsa -out private-key.pem 2048


  

3. Generate the public key, and put it in a file, public-key.pem:

    
openssl rsa -in private-key.pem -pubout public-key.pem


  

4. Hash, and sign the content of the post, then output the signature to a file, post-content.sig:

    
openssl dgst -sha256 -sign private-key.pem -out  post-content.sig post.txt


  

5. To then be able to paste the signature as text, it must be base64-encoded:

    
openssl base64 -in post-content.sig -out post-content.sig.b64


  

If you would like to verify your signature, you could then do:

    
openssl dgst -sha256 -verify public-key.pem -signature post-content.sig post.txt


  

If the signature is correct, then it will return Verified OK

There likely exists other, simpler methods of going about this, but this method is functional.

    
content-signature:CEsuKEwcmfYh/3/04OTscm9G/+JNkIoAELQBxqJYe67O6qCbZZ7IuzFjes4yVVW+ntE6807wy0lmt7TU8obFLHGbVrrb+J8M+Qo/qviftMNKAux+7ASWz/z87UOGieOPRlV6PbWzpMBHdF2A5LFLdpS68adQrLNOjb5JalWRYa2vN4L6BO88doirJmHtQ8TQ4mvaNKYe0BD7BdXQkc9pzivKWVmSdZA7avb8QJLDdukgJCRHgjQXKaLnEZHfmSxfG4mUDcK0bw35GmqYLsVlN0nwj1Xdd1A0bl3sgTgCbpkpb9kdQv4L2HINJ1vCy472qG+cnor4Lt6NpdKIhUR35Q==

  

Neat idea! Although, it would probably be more practical to use a centralized model since if one peer is offline, then the syncing would not occur. That is, if my assumption is correct that you are thinking of directly syncing between 2 devices.

Have you posted a suggestion on github?

There are existing issues on GitHub:

• Option to generate URL previews at the receiving client, not the server
• Consider making the sender generate url previews, as with e2e thumbnails

    
OmPLoYXUOIPhnGr5krVHtCI4knI0pbb4zO/7u4iEWtsBXQbEFOJQITsUYRtvd+9lQvbuKYgEF8tip5O7mZcvgFRNdE2jUR+IE9ewoi5prn7pNTx4+xKR5vgVpXYaixpLI1qMMA+iXD+XobZJRGz9nHi+vzcTMkyHD0X6UpS2GVYztqgghxyxkMhvneR2PtwnjJo/KUi5KAtD4Le/p6wAxS/SZHSzKJIS4vflTayYU/zfZhlc/ElDPy/hoZAeLmq3fWJDMQN5ZPIyS9/mMp+/CkIfRj/GvkDfI2+OdHW23WACezuMHBnvO4w2LPakLDasUKpeUx7bJrNdC1qBcDIDAg==

  

If you look at this documentation it outlines various methods of generating URL thumbnails. Essentially, a separate request from the client for only the URL is made to the server which then returns a thumbnail. It's an absolutely moronic design choice, if you ask me.

EDIT (2023-10-02T01:35Z): Do note that the link that I provided is for Synapse v1.37 -- Synapse is currently on v1.97. Curiously, the documentation for the new versions of Synapse have removed the sections talking about URL previews. I'm not sure what's up with that.

    
RT373YSQwMB+y28d7xm/Xybihcmx9jgkd4RskvPuoFQ3hapIv4exdmtMe+QxsVqos5odxTVuKAftj53zXFFQyD7MK0985zDvfKYjIj+b+8rNSAG0fArG2SXVBW0mLXqRnXiZXiknoPekyu7MKr1aD8k9DMQzCap60oNWmOLoCQXdmEetiEnhGL8zW2KR9P4MxtzxMzLzPWJyLmpLbXVJdxTmHFN32IvMHiyY29iJqZegmIuav0+IP2c3leGrJs75eGW2uWoj8J8VWWzflWfRRO3FwzJFRIvrptPN0osD0wMrgLJ4FYwXZQetIEJ99TxWvxqTYak90q6HxvVygOyHPw==

  

Indeed, it does. It can be overlooked, however. I added that info to my post, though. Thank you for the note.

    
AcN4ig5AQaP5RPDXd4zDkAmFvg+Xp65zI6i5ossToWdpV7Ad2r7s0UAn6TRKG5NbiBOvr+ZWk8fVS8abFcXGEmEp9axEG/BOxJVSMteDTjhf74fVmRbIxik8EpYR2FA5DXTK/r6nrxxiuTTak5kNUrSi2Bb4ebdFEEhrdikuDm68jjHiXsqOS2O4JYxUhhd0qrjnzaCAtiCr1KnqyR+9eEtUDv8nx8IvAnk/9EmzSnPxn5BinJYFjM3qEh3KYyqfY//d0brUQFkbKJmqn1KGdhmzZG7SUtZPsAozJSrVFHynavEwx6SIhxAbJYojQ10RjkYYXVQ10RNmB+NiPs1Zgg==

  

Shall I assume that your snide remark indicates that you have no rationale?

I think lemm.ee has no NSFW allowed

Lemm.ee allows NSFW.

EDIT (2023-10-01T07:00Z): Unless you meant that you can't upload NSFW to lemmee, then you are correct -- you cannot -- that is, aside from the fact that all image uploads are currently banned on lemmee due to CSAM concerns.

Perhaps the next emergent entity is not corporeal, but, instead, of the collective. A good example could be similar to what @kozy138@lemm.ee stated about how the movements of people in crowds are, on the "microscopic" scale, seemingly random, and unpredictable, but, on the "macroscopic" scale, can be predicted quite accurately. One could look at economies, traffic flow, entire nations, etc. as emergent entities that rely on our individual, autonomous interaction. A very interesting such example is outlined in this paper which explains how "Online communities featuring ‘anti-X’ hate and extremism" can be accurately modeled using "novel generalization of nonlinear fluid physics".

I agree which is why we need a federal ban on high capacity weapons.

What is your rationale behind that statement?

The roundness of the Earth is under contention too.

Err, no it isn't. There is a difference between subjective disagreement, and denialism.

Would you mind defining "we don't really know how it works"?

[...] lowest viewership since 2015

Hasn't there only been one other debate since then...? That's rather misleading.

I understand that you don't think it is necessary, but I'm curious what your reasoning is, as to why?

It is important to remember that prior to the 14th amendment, the Bill of Rights was understood to only apply to the states, not the federal government.

You raise a good point about the 14th Amendment. I would argue that it even further enforces the idea that the states, individually, cannot create firearm legislation as it would violates the 2nd Amendment, which, in turn, violates the 14th Amendment.

Another important distinction is the use of the term “bears”. A person hunting deer is not “bearing arms”. A soldier bears arms.

While I do agree that paying attention to the exact terminology used is crucial to the Amendment's interpretation, from what I can see, the definition that you stated is not without contention.

I have found that instances that do seem to modify the source code just use the existing "Code" link and simply point it to their own repo instead.