TLP - Proposing a Novel and Deranged To-Do List Protocol
5 minutes read ā¢
Elevator Pitch
In a world built on innovation, efficiency, and performance, TLPāTo-Do List Protocol stands outā¦
For years, to-do list apps have been little more than demos for new front-end frameworks or hyperscaler spyware masquerading as productivity tools. TLP flips the script:
- Compatible and Flexible: Adapters are on the roadmap to support several popular to-do apps. MIT license and a rainy day means you can support any to-do app you like.
- Secure by Design: By funnelling encrypted packets through your to-do list, youāre holding a funhouse mirror up to hyperscaler data collection. If theyāre going to harvest our data, letās make them work for it.
- Feel Productive Again: TLP doesnāt break your tasks. Your app stays functional! Your personal tasks will be ignored and treated as corrupt packets. With hundreds of tasks being added and completed every second, you can check ādopamineā off your list.
TLP is a groundbreaking, TCP-inspired messaging protocol that operates through to-do lists. Yes, you read that correctly. Your humble to-do list app has been granted super-powers: unnecessary partial re-implementation of the transport layer at the application layer!
TLP is pure joy (and pure overhead).
Checkout the project here! š
What Is TLP?
TLP is a satirical, semi-functional messaging protocol inspired by TCP that uses popular to-do list applications as the transport backbone.
Packets are sent as to-do list tasks, ordered by due date and marked as complete when received. Everything is updated in real-time to simulate the mechanics of data packets traversing a network.
Mix in some disruptive hypey buzz tech, some pseudo-encryption, and we have a winner! Think of it as the most inefficient way to communicate securely with your friends while simultaneously overwhelming your to-do app.
How Does It Work?
TLP is TCP inspired. It maps TCP packet fields to stock-standard to-do list task fields.
Tip
Want to learn more about the anatomy of a TCP packet? Check out this GeeksForGeeks article.
| TCP Packet Field | To-Do Attribute | Description |
|---|---|---|
| Source Port | Task Owner | Represents the individual or entity initiating the task. |
| Destination Port | Assigned User | Indicates the person responsible for completing the task. |
| Sequence Number | Task Due Date | Encode sequence number in task due date to denote its order in a series |
| Acknowledgment Number | Task Dependencies | Last received task as checked first checklist item, next expected task as unchecked following checklist item. |
| Flag: URG | Task Priority (High) | Set the taskās priority level to āHighā to indicate urgency. |
| Flag: ACK | Task Completion Status | Mark the task as complete to signify acknowledgment. |
| Flag: PSH | Task Priority (Important) | Set the taskās priority level as āHighā to indicate PSH flag |
| Flag: RST | Task Reassignment | Reassign the task to a different user to indicate a reset in responsibility. |
| Flag: SYN | Task Coordination | Add a checklist within the task for steps that require synchronization with others. |
| Flag: FIN | Task Closure | Upon task completion, archive or remove the task to signify itās finished. |
| Window Size | Todo List | Group related tasks into a single list to represent the batch size. |
| Checksum | Task Review | Include a final checklist item for reviewing the task to ensure accuracy before completion. |
| Urgent Pointer | Task Priority Indicator | Use the taskās priority setting to indicate urgency. |
| Options | Task Notes frontmatter | Include any extra instructions or information in the taskās notes as plaintext frontmatter. |
| Data (Payload) | Task Notes | Encrypted message as payload in task notes. |
Multicast??
While multicast is usually out of TCP territory, TLP leans heavily on the Application Layer and implements multicast. If unicast, tasks are assigned to an individual. If multicast, the tasks are unassigned and all who are scoped receive the task. Packet acknowledgement then becomes a race-condition. An exciting little competion in an otherwise very cooperative standard.
Whatās Next for TLP?
In the coming posts, weāll explore more of TLPās tech spec and dream about the necessary components to get it off the ground, including, maybe:
- āAdaptersā to interface TLP šš with popular to-do list apps.
- Finding the Unicorn š¦āØ of high-throughput to-do list apps.
- Overengineered blockchain integration š§±āļø for authentication workflow.
- Different methods
Join the Revolution
To-Do List Protocol is a call to action. Itās a powerful reminder of what an industry shake-up can do. Do you know how diffusion based generative models work? The same way high school art assignments work. They throw something random at the canvas, interpret the results and learn from their mistakes.
Join us! Donāt chase the money. stop following the cues. Subvert the status quo.
Joiin us for the next installment of the TLP Blog Series!
Stay productive. Stay creative.