File tagging can easily hit the max filename limit

[OpenBagTwo]

Summary

Yeah, this whole "specify linking intent by tagging each file" concept was a cool idea, but it rapidly became annoying after like 3-4 instance tags. And then for a few of my universal files, I've run up against the 255 character limit common to most filesystems.

Environment and Version

This is going to be an issue for ext4, NTFS, APFS, Btrfs, and pretty much any filesystem anyone would use.

This is not specific to any (current) version of EnderChest and is instead a flaw in the very premise of this design.

Steps to Reproduce

Take a given file and attempt to tag it across enough instances to hit that 255 character limit. A good example would be my screenshots folder, which I want shared across all instances.

Workaround

If I have one file or symlink named:

screenshots@instance one@instance two@ instance three

I could create a second one that continued on

screenshots@instance four

that pointed to the first file (or the common target)

Severity

This, compounding with a few other QoL issues surfacing from daily driving EnderChest for the last six months, invalidates the entire fundamental design of this project.

Desired Outcome

Pick a new approach!

Urgency

I do not believe EnderChest can "go live" using this paradigm.

[OpenBagTwo]

This will be resolved with the completion of Milestone 2