Torrent Talks: Difference between revisions
Jump to navigation
Jump to search
m (https://sourceforge.net/p/flightgear/mailman/message/36622733/) |
|||
Line 5: | Line 5: | ||
(And indeed Bittorrent might be one solution)<ref>https://sourceforge.net/p/flightgear/mailman/message/36622733/</ref> | (And indeed Bittorrent might be one solution)<ref>https://sourceforge.net/p/flightgear/mailman/message/36622733/</ref> | ||
== Idea == | |||
== Prototype == | |||
We need to actually write a prototype, using libtorrent (or whatever is $sexy these days). Which would be welcome, just keep in mind it has to be a library solution we can ship as part of FlightGear, including on macOS and Windows: which means no weird malware installation or Windows Firewall warnings about us looking like malware...<ref>https://sourceforge.net/p/flightgear/mailman/message/37109357/</ref> | |||
== References == | == References == | ||
{{Appendix}} | {{Appendix}} |
Revision as of 18:09, 23 September 2020
This article is a stub. You can help the wiki by expanding it. |
Background
So while 16k textures are lovely, we should definitely figure out a hosting + delivery method which is opt-in, and doesn’t overload our current we-get-it-for-nothing providers :)
(And indeed Bittorrent might be one solution)[1]
Idea
Prototype
We need to actually write a prototype, using libtorrent (or whatever is $sexy these days). Which would be welcome, just keep in mind it has to be a library solution we can ship as part of FlightGear, including on macOS and Windows: which means no weird malware installation or Windows Firewall warnings about us looking like malware...[2]
References
References |