mdtimesheet VS wdt

Nice one! I made something somewhat related a while back... I still use it.

https://github.com/keyle/mdtimesheet

There is nothing like solving your own problems.

As a side note, I was capturing all my side projects via plan style files,

so I wrote a time tracker for it following a simple format that would calculate roughly how long I spent on each project.

https://github.com/keyle/mdtimesheet

Update:

https://github.com/keyle/mdtimesheet

I like the way you're thinking here, I think the limitations you mentioned with gemini may stand... for me it's kind of like the limitations generally speaking with markdown. Doesn't leave much room for doing stuff like parsing the raw data when they aren't in a hierarchical structure with xpaths you can target and stuff like that, it just throws out so much baby with the bathwater that I'm ready to scream infanticide.

Any thoughts on fast experimental protocols like warp data transfer [1] or fast and secure protocol [2] ? I know they're not exactly the most open things or wellsupported in terms of what you're looking for but I've been really wondering when we're going to start seeing pressure to relieve network congestion using stuff like this.

[1] https://github.com/facebookarchive/wdt

That's great stuff, I wonder how it compares to wdt[0] when there's only one TCP path. This has been my go-to tool to transfer files on the network.

0: https://github.com/facebook/wdt

I guess? If you’re building parallel infrastructure (vlans are not enough obviously) just for running Aspera over it might not be the worst thing ever, but that’s an expensive way to live and that’s before you pay for the A$pera licenses. There are free and better behaved platforms out there like https://github.com/facebook/wdt if you don’t want other applications’ TCP sessions to time out while you’re trying to squeeze out the last half percent with Aspera.