Diaspora* "Post Killer Button" | Tidy up servers and give users control

@karthikeyanak I'd like that, too. :)

Are you just wanting that feature or are you going to implement it?

@rasmusfuhse it's just an idea of mine, but I'm not able do code it. :-/

But I guess it's not too hard to implement?

Okay. But then your proposal is nearly useless. I mean, it's great to gather ideas and create concepts. But we don't want to use loom.io as a wiki, but as a decision-tool. So most of the times a proposal here is asking which way diaspora should go. So if your proposal is going to get accepted here all it says is: if someday someone is going to implement this feature, the pullrequest should not be rejected with the reason that some other one thinks the feature is useless. But this usually doesn't happen - may there be a decision about it or not.

By the way, we have a wishlist thread. Goob is the man for the big vision here and he started the wishlist: https://www.loomio.org/d/VMg5HlpZ/diaspora-the-next-12-months

Deletin posts in decentralized social networks is quite complicated: How can you know whether other pods actually delete posts when being asked to do so by other pods via federation? As Diaspora is open source it'll always be possible to get the source, comment out the deletion code and collect posts.

As deltion doesn't even work reliable for single posts, we shouldn't implement a "post killer" button which makes people feel safe when they aren't

@thomasl I guess only a few person would be against adding a feature. The problem is, who is going to implement it? It's not about "it is not hard to do it", it's about the fact that we all are volunteers and have very few time to work on diaspora. So request a feature is useless, we need people to implement it, not ideas.

This is a good tool to lost sensitive data. Suppose that before pushing this button any normal user will walk through all the posts in a desired period to examine if he wouldn't delete any good stuff. For those who don't have a good posts I'd suggest an option in settings to delete old posts automatically.

@thomasl I'm against deleting reshared posts as well. It could lead to confusion.

I'm loving reading old posts, too. But I can understand your point. But as stated above by others, I consider it rather complicated …

@trollischmittlauch maybe some type of user image of code that compares it to the pod your on as regards to options available. or a podupti link and addition of a features available to the podupti list of pods.

As far as post killing. other's add comments to a post and maybe liked their comments on a post.

So we could add a general description saver that with added effort anybody could fill out once then maybe a process of sticking with a post definition after whichever process of social collaboration.

This general description saver either creates a community user which is showed to have made the previous statement of a real person. Say when I delete a post then John Do is now the new poster.

or else if it's like a article or picture a generalization box cold be put in its place saying "it was a picture with these qualities" or " it was an article with these qualities" Then the comments could still relate to it.

Agreeing on the New Diaspora Community Post Attribution re-licensed to Avatar would be the new and edgy social media thing. Could be done Diaspora whole or Pod specific

Using a regex code;
we could turn all comments contained within the deleted post that refer to the original poster by name to turn into @JohnDo or whatever the community post reattribution avatars name is agreed too.

of course we'd have to make sure it covers and comments where the posters name was mentioned in the forms of; # , @ , markdown possibilities like , or just regular type like this

Tidying up the servers could include options of html 5 browser data holding and serving so users can save certain posts to their own computer and serve them only when their online?