main
parent
2f80c40c1d
commit
a52850e43c
|
@ -1,7 +1,9 @@
|
|||
# Top 10 TODO items
|
||||
# Top 10 TODO items by priority
|
||||
|
||||
- Integrate relay server into `ptth_relay`
|
||||
- Allow lazy P2 --> P3 connections
|
||||
- Allow multiple relays in P2 GUI
|
||||
- Split client proxy into its own crate to isolate FLTK dep
|
||||
- Integrate relay server into `ptth_relay`
|
||||
- Integrate server proxy into `ptth_server`
|
||||
- Auth for client proxies
|
||||
- Auth for server proxies
|
||||
|
|
|
@ -0,0 +1,15 @@
|
|||
# Pie in the sky ideas
|
||||
|
||||
These aren't good enough for the main TODO list, but I think they would be
|
||||
cool. Most of them are a combo of "Too much work" and "Too little demand".
|
||||
They're not weekend projects with obvious payoff, they're month-long projects
|
||||
with a high risk of failure.
|
||||
|
||||
- Custom VNC protocol that uses datagrams (Would need to forward datagrams
|
||||
within PTTH too)
|
||||
- Cross-platform pull-style backups (Doing backups well is its own field of
|
||||
study. But I think convenient pull backups are worth it, even if they're
|
||||
not as perfect as Borg)
|
||||
- Remote shell for Windows (Just admitting that PTTH is basically malware
|
||||
minus the mal)
|
||||
- Generic file send / receive with a decent GUI (This is actually feasible)
|
Loading…
Reference in New Issue