Kind of. The default behavior is to create a new link. So when you grant someone access you are actually creating a new link. However, you can find the buried manage access settings and change the permissions on the original link. If you do that then they can use the original link.
(Teams makes this Byzantine in the extreme to accomplish as you have to go find the folder it drops all shared files in to gain access to manage access settings. But it does allow you to retro change access even for things shared in Teams)
Yeah, many things are definitely possible but to me it seems like the user experience is driven by the technical implementation and architecture, instead of vice versa.
From the outside looking in, it's the age old organizational problem when there are no good synergies between customer experience and development teams.
Technically, you could do this in Mylio but probably not in the way you want.
Mylio stores “Live Photos” as
Photo.extension <- the “photo” it shows in the interface
Photo.xmp <- all the metatdata
Photo.myb <- everything else
Literally the myb is just a zip of everything else associated with the photo. So in the “Live Photo” case that would be the associated video file. If you have edited the file in Apple photos that also includes the XML Apple uses to non destructively perform the edit. As well as a copy of the original photo.
In your case you could just manually create the myb file by zipping up all the associated extra photos and changing the extension.
However the interface would only show the single main photo.
We believe that all of the vulnerabilities we discovered have been mitigated by Threema's recent patches. This means that, at this time, the security issues we found no longer pose any threat to Threema customers, including OnPrem instances that have been kept up-to-date. On the other hand, some of the vulnerabilities we discovered may have been present in Threema for a long time.
For what it's worth, and obviously I could have been clearer about this: what's interesting about that link is the description of Threema's design, not the specific vulnerabilities the team found.
Beware of the hidden catch here. The account that adds the credential to the group “owns” it. So if that account goes away for any reason so does the credential.
Could have been clearer but it is there. Here is the relevant section. In short single entry is basically the Account view and Double entry is the full ledger. (Called double because of the hard requirement that all Entries come in pairs.)
> Ledgers are conceptually a data model, represented by three entities: Accounts, Entries and Transactions.
> Most people think of money in terms of what’s theirs, and Accounts are the representation of that point of view. They are the reason why engineers naturally gravitate towards the “simplicity” of single-entry systems. Accounts are both buckets of value, and a particular point of view of how its value changes over time.
> Entries represent the flow of funds between Accounts. Crucially, they are always an exchange of value. Therefore, they always come in pairs: an Entry represents one leg of the exchange.
> The way we ensure that Entries are paired correctly is with Transactions. Ledgers shouldn’t interact with Entries directly, but through the Transaction entity.
The backup situation is terrible
- Mac only
- Only Passwords (no passkeys)
- Only items you created (so nothing shared with you, even if you own the shared “group”)
In short your only option is one at a time manual export
Hmm any suggestions on how to convince it to produce something like this?
I have lyrics that I want sung by a solo female voice with the background being a male chorus. Something reminiscent of a woman singing the details of a David vs Goliath type battle backed by a chorus of the victorious warriors from that battle.
So far I have completely failed to be able to generate a female lead with a male chorus backing
(Teams makes this Byzantine in the extreme to accomplish as you have to go find the folder it drops all shared files in to gain access to manage access settings. But it does allow you to retro change access even for things shared in Teams)
reply