Granted I rehashed over what a few of you discussed on this and other related/linked topics but I feel the same way about it's cleanliness and feature being more evolved than other sites. I think it could be worked in with current database structure and no need a rehaul or breaking of existing duplicate posts, leaving those as they are. Simply by adding another field or column that is a reference id, if it's blank show the post as usual, if it's not blank, on the client side silently show the original/main post automatically.

I couldn't seem to find right keywords in search for this issue, luckily before posting I kept scrolling through other issues. The cross posting is something I had on my mind for a while, and with FA, got annoying that I found duplicates of a bunch of files that I forgot I had downloaded simply because the file name was different between the artist and commissioner.

I imagine this would be solved by using like computer programming 'shared pointers'. Have a counter on the submission for how many places it's linked (artist, commissioner, potentially the groups idea) so it doesn't fully get deleted off the filesystem or the submission id and comments don't get purged unless it fully reaches 0 on the counter.

This is mostly relational database thinking, but a nosql style concept would be even easier since you don't have to have a 'field' or 'column' you don't need, making those entries even lighter, but for the gallery database for users, have the submission fields all blank but there be another field that's hidden that's a reference submission number. So under my gallery if a normal submission has (id, owner, name, views, favs, description, tags, publish_status) you'd have those fields all null (except id, probably, as primary keys are required) and so it'd just be (id, owner, reference, publish_status), and then on the client side you would on the infinite scroll or gallery request simply silently replace the thumbnail and feed items with the real submission. This way if an artist on upload or commissioner on upload puts in the new artist and commissioner fields (with + button, so if it's a group picture everyone gets the attach) and then they get it as a pending notification to approve/add or reject it before it shows up in gallery automatically so there's no spam tagging or trolling. Then since it's technically still submission row in database, you can delete it from yours and it still stays on the artist or other participants, and you can hide it in drafts/unpublished since it's still a submission row for your gallery. If you delete it you can ask one of the other participants to readd your name in the participant field with the + again or maybe just a small option in dropdown like where 'report' would be that would be like 'request particiapant/featuring link'.

This way you can have a single copy of the file on the sites filesystem (saving probably 1/2 of all uploads, since almost everyone uploads commissioner and artist side) as well as converging conversations which would help make each submission feel more alive and interactive. Artist may not get 'this is well done' comments and be discouraged since they're posted on the commissioners version, and total up the favs and promotes nicer.

This would seem a little patchwork and potentially waste some row space if relational database with fixed field widths, the empty columns would take up bytes of space regardless, but it would only require adding Artists and Featuring fields in the submissions table and using the + feature of tags currently for the UI side, as well as adding a field in submissions table for a shortcut/reference to another submission identifier.

After implementing, can also possibly do a moderation feature to merge and resolve issues with existing duplicates (if requested by participants) so the small backlog could be left as is or slowly wittle down over time with the sites still (relatively) small submission quantity.

#3 for sure.

That's a browser issue, left clicking download automatically downloads directly to my /Downloads folder on Chrome and Firefox and Android Browser/Chrome at least.

As far as file name issues go, that's under another vote that has been responded to as being in for when site launches, right now it's a hash id number but will be fancier naming of artist and submission id when out of Beta.