Though, not the same thing. I really like the Dutch implementation for their old maps: https://topotijdreis.nl
take6056
Another Many-to-many example within this usecase would be "subscriptions". Users can subscribe to multiple channels and channels can have multiple users subscribed to them. You would use another relational table that stores the channel_id & user_id, with uniqueness for both together, since "being subscribed to one specific channel multiple times" doesn't make sense and perhaps put a column to store "hitting the bell" in there too.
This is a pretty interesting counter example: https://www.eteknix.com/running-yuzu-on-switch-gives-you-better-performance-than-native-gaming/
But, as others have said, exceptions confirm the rule.
You can cancel when receiving the first reminder, or probably also immediately. Good initiative though, I might do the same.
At college some guys were self hosting a git server for a project but it went down. We resorted to a USB stick that acted as remote
and was passed around. That was awesome to see, for about a day...
Thought it was a good opportunity to potentionally learn something new. Seems to have worked out.
I'd change
- Github, ... To
- Git, for version control
Except it's barely in your hands because your surroundings have vastly more influence over what you actually become.
What a metaphor.
Thanks, that was an interesting read! I always felt IPFS wasn't ready yet, but the value it tries to provide of being a file system, I've found no real alternative to. Very good to read that iroh is willing to look beyond the IPFS spec to provide its values with better performance. I hope it works out.
It's been a while since I've watched it myself, but remember them going into the ownership structure.
https://www.youtube.com/watch?v=hNZy603as5w
There's basically no way for them to not make it a subscription model.