Kalcifer

joined 1 year ago
[–] Kalcifer@lemm.ee 1 points 1 year ago (5 children)

What you think adds a feature actually takes away a feature (being able to edit posts without the edit being visible). That isn’t a bug, it’s a feature.

Do note that a feature's mere existence doesn't necessitate that it must be a good feature.

Increased hosting costs to operate it (storage)

I don't believe that this is much of an issue, as text is extremely cheap to store. It would, of course, be false to state that it doesn't increase the cost at all, but I would argue that the increase in cost is most likely small enough to be of little concern. Let's make a very basic, and not overly precise example: Say, on average, there is 100 words in each Lemmy post's body. And say, on average, that a user will edit 10 words. Now, say that the algorithm that generates the changes, only stores the changes relative to the previous content, so we can then simplify this to say that it only stores the text plus, say, maybe 1 extra words worth of data for location, and linking information. So that means that each post will only add on maybe 11 words on average which would equate to a 1.1% increase in text storage requirements. Given that all of Wikipedia's Engish article text is around 20GB, a 1.1% increase in that is only about 220MB -- one should be able to see that the equivelant for Lemmy wouldn't be that terrible.

Increased API calls and sizes (bandwidth)

I'm not sure that I am qualified enough to make a comment on this, as I am not at all an expert in how Lemmy's (or ActivityPub's) Networking works under the hood, but how would this differ from how it already works? You can already make an edit, so the number of API requests should stay somewhat the same. The only thing I can think of is that when someone opens the edit history, they would need to make a few API calls to retrieve it all, unless all that could be retrieved in one call, then it should be the same as displaying the date of the last edit which is a feature that already exists with the only difference being the payload size in that case.

99.999% of feature use is just typo correction

Sure, but I don't see this as a counterargument. The whole point of it is to be able to verify that it is indeed a typo correction.

99% of users won’t use the feature

True, this could be seen as an investment that may not be worth it as it would really only cater to those who are, perhaps, on the upper end of paranoia, or overly persnickety.

It invites users to review people’s edit history and nitpick/call out things that the poster edited out for a reason…

This is a fair point. I hadn't considered this. I do think that it wouldn't be super common, it is indeed a possible issue.

Which in turn breaks down and chills conversation as users have to be overly careful that their comment or post is 100% accurate to avoid getting nitpicked, that they fully agree with what they’re saying as they can’t take it back or edit their stance/opinion in the future, that they don’t reveal anything sensitive by mistake

I mean, it's kind of already like this, is it not? What you say is certainly under scrutiny by the court of public opinion. Unless you mean that one cannot take something back because it would be ingrained in the edit history, but, to that, I would say that one can still delete their post.

It invites abuse from mods by reverting edits and dictating which “version of truth” of a post is the one that everyone sees rather than the user being in control.

Hm, I think this is a completely separate issue. A mod, or admin should not be able to do such things. This actually brings up a separate idea that I had where, ideally, a post would be signed by the user who wrote it so that one could be certain that it was the user who indeed wrote the post, and that it was not modified by an admin, or some other external entity. This censorship is an existing problem with no solution.

Extra UI cutter is needed to handle the feature

The button that would contain the history already exists in the form of the edit pencil that posts have. Unless you mean the diff itself, but that would only be visible if one toggles it.

If a user posts credentials, they have to delete the entire post or comment and even then, the backend server very well could still have that log saved in a backup (legal ramifications)

Yeah deleting would be the only option -- personally, I don't see this as a huge issue, but that's just me. As for the logs, they could already exist for a deleted post anyways. When you post something online, there really is 0 guarantee that you can ever remove it. Generally, one must accept that whatever they put online is out there, in some capacity, forever.

Users could abuse the feature to e.g. share links to abuse material and hide it in the log requiring moderators to have to review all messages and all edit histories, greatly increasing their work load, especially if users constantly edit their posts to make moderators jobs harder to sift through all the edits to reveal what they did.

Good point. I hadn't considered this issue. I would argue that it's the most important point of your list. I'm not sure that there is anything that could really be done about it. It would essentially have to rely on someone reporting it after having gone through the edit history, or a mod just happening to have gone through the history themself.

will have a direct, chilling impact on all other users.

Aha, you don't need to use such melodramatic language to try to magnify your opinion -- your counterarguments should be enough.

if you need audit logs, you do it behind the scenes not in the UI

Do note that this is supposed to be for the benefit of the user, and not the admins. A user cannot access logs.

Visible changelogs on information chat / social systems make people talk less, not more.

I would like to know your source for such a statement.

And given how Lemmy is still in its infancy and hasn’t reached a critical mass, adding a feature like OP proposed could make Lemmy a far less inviting place to socialise.

This is a purely subjective statement, I would argue.

[–] Kalcifer@lemm.ee 2 points 1 year ago

This one actually isn't so bad. If a person opts out of their edit history being shown, at least this would be a sort of red flag for the reader that should trigger skepticism in the content's trustworthiness. That being said, it would still be inferior to having a mandatory edit history.

[–] Kalcifer@lemm.ee 1 points 1 year ago (4 children)

Editing a post may be to remove the password or email address you accidentally copy pasted in, or removing some potentially doxxing information, or one of many reasons you want that content gone.

Why not just delete the post, and then make a new one with the correct information?

Github has edit history, but it also allows users to delete revisions so it seems your main concern would not be resolved by this implementation.

If this were to be allowed, the edit history would then be pointless.

And as you point out, there is already a message that says the post was edited and what time.

That is the only information that is provided. One is unable to find out what was changed.

[–] Kalcifer@lemm.ee 5 points 1 year ago (10 children)

Nah, never liked the feature, wouldn’t appreciate it here.

Would you mind elaborating on why you feel that way?

Side note, external images can be embedded in markdown like this:

![alt description](https://example.com/cool-image.png)

Thank you for that info! I'll update my post.

[–] Kalcifer@lemm.ee 2 points 1 year ago

Your are absolutely right. I guess I had accidentally copied the wrong link. Thank you for letting me know! I have now updated my post.

[–] Kalcifer@lemm.ee 1 points 1 year ago

Post a link to a channel of 1k users and 1k users send a request to the website, instead of only the server once?

That would only happen if the URL is generated on the recipients side. What Signal does, for example, is it generates the preview on senders side, and sends the preview with the URL, so the preview is only generated once.

/edit: From a privacy standpoint I’d really trust my chat server provider over random websites. So I definitely don’t see how it’s a terrible choice for these two reasons.

What do you mean? How would "random websites" come into play?

That being said, if you’re concerned, disabling previews is the answer.

Thankfully, they are disabled by default.

content-signature:qGFf4UPQ4M6XKPDbSyjOuKK5erMVrib4GPgJTPSifQT6qiijr1MRJxucdCk8rBol/AB+Blsv+aVn1zxs6D8cHttXu7E0uZuGYuS1UyYq/sVyjW6XSgvwpMqmozHaLh61+je8LDeFXVyR8t+okNYEzugMcmZsbes4gPchoxkkk9Mpo9AzIkmh40JEiz3WTrLMOT6Kwc5B0SIu3QENq2ucqSPUJ9HfOM4yMhYV57wQgk6VyssUWRlntq9RD3gauVa2CKi7g21LppoUiVRoxuxlalXM6azmza4M1z3cAK/F2x8ZEaeQbHjec3Q8LD4/w50dWN5hhuRyGdQTRqY+U0ACLA==
[–] Kalcifer@lemm.ee 2 points 1 year ago* (last edited 1 year ago)

For more in depth information, I'll refer you to this Wikipedia article on digital signatures. But, the long and short of it is that I distribute a public key which would be used alongside that signature to verify if that signature was generated by my private key for the content that is contained in the given post.

content-signature:Hdv6ZJpsd8MxqdThHqSL5gs/cQ+AbxhOPdoRYYOyL8Ip4/dA6VM3oWtTvItLLO1x+I8DiS+Al7ay5e4TasdNNvrXh5cFmq7+b/L523/tJTqheCpv4tNDETp2H6FY9tJa0HmtmIv4jskdeAMrV0Rnmf1HoqMjO729mGdi1fGxLKVIszlBc4TUKtwzLOOFqBYR5zJCeRw7hbNydGnFRCcJcKfhTX/ANkRChqmCU8AR8Vnb99IMUnchWosjno/88WyoVZEpp/M06iMhw63wKsLzwfDySES3UbMAQwLOEYYtC3B8Y+ApeySAfUkssQjVy7bQUtiE7t/5eYoOTCOBQMUJpQ==
[–] Kalcifer@lemm.ee 2 points 1 year ago* (last edited 1 year ago) (2 children)

I don't. The string at the end of my comments is a digital signature which serves as a means to verify that I was the one that posted it, and that it wasn't modified by an admin, or any other external entity.

content-signature:GHnwqVFVDJFDAGt7Xg1oQecp04BoH+qJucdpFOblrg+YxSx8Vp7DfxEQudqcxK1+7yiOjgKvnVDCRP6oU7XTjttdl6sdMpFq9LcFHQ6OlVtjsvaSoIobck4ARimWs5vvTYMTBp6kCNYmhczFniJ52q3Blps7G1bw5q7sOf1z4rWG+CB99jb//02+x6KVjllnoiZJdVhqfa69dryG49W8QxTLvHqr20kTmAQzEpAK/kWgGL2/FLNhUYjvmVQtQAUJlXo/GJtj93AHyrApqwXEVmGSe/imIrosGgugG3UZSRGJzYd+/KwOVxsZNkTe+eMIyV8ceeouy9LcorEKJ1mq/g==
[–] Kalcifer@lemm.ee 1 points 1 year ago

Are you replying to the following?

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.

content-signature:MPvnKfx103YjaEk1xAXkZad4N/0g8T26skCzlxub/U2C7YlNL3ycnBO+T9uLoaM1EJ93KjJxWFjisQOWL6sw6znCkte+v0HXg6SP1KewjQGthXuEwCkFNvbmgNMs/yB9UCnqHQA94fdb1NKgi6NpZqh/Ja6cn6B/fsLAyOtMSAEtmYJWG/Dqa3I9p5GdHXUlMsWpKpZrd4oQ8qxDIDZPYgApZPhNKLHJijZK0lrsj91HbSapgCPY9gGVwT758MnEQ4MdgmywfwFlXxhzPU3qDLu6J/tqjNAPNiPdadE9VN9H/Oj5C2I235zLgmk9TCdMoNz1ZwjpXfg566OZxsjWog==
[–] Kalcifer@lemm.ee 0 points 1 year ago

Someone walking up to you us bad, but it isn’t a credible threat to your life.

It entirely depends on context.

youtube should be held liable for incentuvizing this behavior

For one, YouTube isn't directly incentivizing it. The existence of money, and social fame are the main incentivizing factors. YouTube simply provides the platform. Holding YouTube accountable for this would carry enormous ramifications for the rest of the internet.

even if it means repealling section 250

Do you mean Section 230...?

On the other hand, you shouldn’t start a shootout at Walmart over a tik tok.

That is a rather reductive statement -- you are ignoring crucial contextual information. The victim assessed that, given the situation, there was a credible threat to his safety, and acted accordingly.

content-signature:dD+9B0nz63HWVwijeZIDB4gx0Ac++yPYtxsZJAd2m54y8qUwqFBgmQpjYkX5x8Xg/ERu81hD8Ar01Kmx06y+g/lznsz1YP6Hixn1qwK+0ydI4rONqDgWE33kcccF1tzBND93DpQDvgkkTPgrRq9cvakW42YgS8AJkrVgpGGkbMQmAD+1WosMncwtZRb3iObhjgf6qq7idc3wqpjsLsxvK9i476EK+9hygKwWwLwL7vAvX++igd8G0XARr7xeBA7oUcmc89OsF2CE9LEf4FUEsW3b9TMv57CFGu0WYpivqglJTKg/6F4VCKm9u/l7FT8E83MDqgtPHjx6CMvydWjPag==
[–] Kalcifer@lemm.ee 1 points 1 year ago

It seems like the best outcome would be: person having their personal space invaded tells the “perp” to stop it.

The best outcome, sure, but not a guaranteed outcome.

judge orders to cease their invasive harassment against other people.

That's not really how the law works. If It is already illegal to harass people, then the court order would essentially be along the lines of "I order you to stop doing illegal things!".

The whole being shot just shows how quick to violence and homicide Americans are. It’s like, the solution to everything these days. Dealing with people the past few years in public is pretty dicey, just asking someone not to cut in front of you at the checkout line could potentially lead to a mass shooting these days.

It isn't entirely fair to group unprovoked violence with self-defence. There is an argument that could be made for proportional response in defence, but this is a separate issue.

content-signature:pAJkBsbiDHXMaSZ2SkenLgap0KT3Jnz3LV4F7n97GHsbMXIAVNZFFnsd4WxHZ6ryOSW6OvoT+fWGWCrTyCFjAH/IjqtLbk2uPqIXBNRAFv6AGQ3swX6kqtpKe97t35Of+ACUgyXM4BX0HGpoEojRhuHrKUU2EAD8brvTkHBVIXD5QTDWibmEm6aUZpnfCmBLoAyo8J/uiN1NBnbYZghJ9vgG8JVIo26MNFeP9Vq79LihQ0wp6PXHiS38+M4YQ65wk+cPKWXgxYfg4N/VNdsQkoAtEk4OVnMAZoh42eBiGNbTcp2xB4V9Qwk+eCkn1POi1DTKb7NYjpi03kj1lvRX1A==
[–] Kalcifer@lemm.ee 1 points 1 year ago* (last edited 1 year ago)

Using a bot to generate a URL preview is an interesting workaround.


Content Signature: cLObDckmLviCA8xG832rJ8PFk9UTYN/PrdRb5/lCZkl+GsjtkMp90r6PWD+Ffxby0izyxVeDocLbJh8xrP7L3a1dUX2whEABb8mAhl+cHJqbxq07Z3SWBcroLyolMjmIfUQIgRRRB6lUhbsiwCfKcoVrf0HQchXZS+83YcyMtr+dgiIhVQar3/WMkIk+4nJ/sS+O2vz7c/RfxAzYYzFSPErFVe8Y1NWXWqPOajV/BdLS0U8239ElxUb7Q2Zq8SCgzqoOBtFbgWXTsa6lHFj4gqkRiaDzH6jlJhuO4rRZdA6E2dP+G0Ru7MexI1P6ev65I6VMWxYye0nqtdXC8Alp3A==
view more: ‹ prev next ›