Actually the behaviour is different. I tried to replicate the problem. I renamed the file not to use 'first' in the name, it's misleading.
# Steps to reproduce
* create a file $HOME/Ubuntu\ One/foo-bar
* publish $HOME/Ubuntu\ One/foo-bar
* rename $HOME/Ubuntu\ One/foo-bar to $HOME/Ubuntu\ One/foo_bar
* create a new $HOME/Ubuntu\ One/foo-bar
# Current result
Nautilus thinks that the foo-bar is currently published, and the initial, renamed foo_bar is not. What really occurs is that copying a public URL from the "oh-so" published foo-bar copies a public link of foo_bar! So it looks like the problem is revealed on the Nautilus side. We never publish a file that user has not explicitly published on his own.
# Expected result
foo_bar should be published, foo-bar not... - that's the case, but public URL of foo_bar is "attached" via context menu to the foo-bar file, and this is the bug.
Actually the behaviour is different. I tried to replicate the problem. I renamed the file not to use 'first' in the name, it's misleading.
# Steps to reproduce
* create a file $HOME/Ubuntu\ One/foo-bar
* publish $HOME/Ubuntu\ One/foo-bar
* rename $HOME/Ubuntu\ One/foo-bar to $HOME/Ubuntu\ One/foo_bar
* create a new $HOME/Ubuntu\ One/foo-bar
# Current result
Nautilus thinks that the foo-bar is currently published, and the initial, renamed foo_bar is not. What really occurs is that copying a public URL from the "oh-so" published foo-bar copies a public link of foo_bar! So it looks like the problem is revealed on the Nautilus side. We never publish a file that user has not explicitly published on his own.
# Expected result
foo_bar should be published, foo-bar not... - that's the case, but public URL of foo_bar is "attached" via context menu to the foo-bar file, and this is the bug.