Rosano

Here are the headers I can see in Safari: 

> But that would put the responsibility of making sure to not overwrite any existing files unintentionally to the app, not the library. I wonder if it's merely an edge...

> I'm wondering if we need some kind of force-overwrite argument for the PUT functions, in order to ensure that implementors are aware of the situation. Oh yes it would...

Is there any documentation on how to manually resolve conflicts? I have found the following links that describe some things but I'm still not sure what to do practically speaking:...

I just found the following in #684: > But instead of this now firing a conflict event, the request is repeated indefinitely. I wonder if it has anything to do...

I was able to stop the conflict event from firing repeatedly by updating the object inside `setTimeout`. I'm guessing there's an issue when 'conflict handling' happens synchronously.

> hmmm. I guess “[email protected]” or “[email protected]” is the full federation user ID? I guess if Fission supported Webfinger then the app would probably initiate the process outside of webnative...

Perhaps related: if the username/address was encrypted rather than stored in plaintext, the recipient could assume it is the actual identity? Again with my funding system, I can tie things...

I put the example back up, you can try dragging the `input` from the first section. I don't really need this anymore though so feel free to close.

My impression from upgrading all my apps in the last months is that: - clients with incomplete data due to this issue pre-upgrade may not 'fix' themselves; might be helpful...