iOS 26 fixes this with an option to only show photos not in an album.
Additionally, if you are backing up photos to a hard drive you will be much better off using an app like PhotoSync. It has a one time payment and transfers direct to whatever you want with far less errors and more control than Apple’s terrible buggy disaster that is transferring photos by wire.
I’ve been working on a small browser app that is local first and have been trying to figure out how to pair it with static hosting. It feels like this should be possible but so far the tooling all seems stuck in the mindset of having a server somewhere.
My use case is scoring live events that may or may not have Internet connection. So normal usage is a single person but sometimes it would be nice to allow for multi person scoring without relying on centralized infrastructure.
I may end up doing that, but I really wish there was a true p2p option that doesn’t have me relying on someone not rug pulling their free tier sync server.
Yeah... true p2p is pretty hard though, to the point that even stuff like WebRTC requires external servers to setup the data sync portion. It would be nice to develop something that worked at that layer though.
IIUC, InstantDB is open source with a docker container you can run yourself, but at this point it's designed to run in a more cloud-like environment than I'd like. Last time I checked there was at least one open PR to make it easier to run in a different environment, but I haven't check in recently.
I spent some more time hunting due to this conversation and I’m hopeful that yjs + y-WebRTC + PeerJS will solve this. I also see that there are a few libraries that enable QR codes to replace PeerJS as a truly offline WebRTC initialization with true p2p connectivity. Looks quite promising
Unfortunately, p2p is *inhales* fxxxed! due to how modern internet networks are set up.
NAT (potentially VPNed at carrier level), lack of IPv6, firewalls blocking incoming traffic, dysfunctioning UPnP, blocked UDP. Next tier issues: legal, that bound user identities to IPs, showing your IP publically is a privacy risk first and a security risk second (DoS).
It seems like it'll be impossible without an overlay network (like Yggdrasil, i2p), but these will be too heavy for mobile devices without a dedicated functioning relay... here we go again.
This reminds me so much of what I really wanted to do after reading Piranesi by Susanna Clarke. It seems like such a perfect setting for an ambient soundscape like this with the ocean sounds crashing through the rooms, various birds passing through or collecting, you could even add drones for the statues. The rooms, ocean, and wildlife are perfect for procedural generation. Only the sculptures would be a bit tricky to infinity vary.
In short thank you :-)
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.
Additionally, if you are backing up photos to a hard drive you will be much better off using an app like PhotoSync. It has a one time payment and transfers direct to whatever you want with far less errors and more control than Apple’s terrible buggy disaster that is transferring photos by wire.