What I'm having trouble understanding about the whole thing, and the author really misses the point by talking about Snap and Flatpak, is that the technical rea

What I'm having trouble understanding about the whole thing, and the author really misses the point by talking about Snap and Flatpak, is that the technical reason Dropbox are only supporting ext4 is apparently the use of extended attributes. Now, correct me if I'm wrong, but a filesystem is supposed to abstract these concepts. All current major Linux filesystems (ext2+, btrfs, XFS etc.) support extended attributes. The implementation is irrelevant. It should be exposed to the application in exactly the same way because that's what the filesystem is /for/. Dropbox shouldn't need to worry about this whole thing because they should just be able to call the system API to deal with it. Or have I fundamentally misunderstood the issue?