nickzelei
Joined 4 years ago
Joined 4 years ago
I remember using it to chop wood. Thought it was so crazy cool that you could do that. Stopped as I didn’t wanna get banned. I was also afraid of the ent that would kill you if you weren’t paying attention. This was also the time where your axe head would randomly fall off.
I finally got around to installing it as I got an xteink x3 and wanted to have cross device syncing back to my Grimmory server. Works great with OPDS and KOSync.
Although I miss using the native kobo sync where I could just add a book to my virtual shelf and have it auto sync to my device. OPDS seems very rudimentary in comparison, but it works nonetheless.
It’s a no brainer at the cost even if it’s not saturated. 10 gig equipment is expensive so majority of my LAN is 1gig. I ended up getting some new network equipment and my WiFi caps at 2.5Gbps.
Steam and Usenet are my primary downloads that can take advantage but even my NAS only has a 1gig card as I haven’t bought the 10gig upgrade card.
Majority of homes are most likely fine with 1 gig, but we also don’t know what the future holds for network bandwidth.
As a result, I came across this absolute gem of a website! Glad to see it here as it's a wealth of knowledge. Who knew there were so many ways to tie and lace up shoes. There's even methods to design your own! Amazing.
They were both $20. The keyboard one works fine. I’d love to have a kvm like this but the price certainly gets gives me pause when I got halfway there for basically $20-$40.
I haven’t looked at the code too much(yet). I’d be curious to know how you’re handling some of the more wiry edge cases when it comes to following foreign key constraints. Things like circular dependencies come to mind. As well as complex joins.
I feel ok posting this because it’s archived, but this problem is basically what we designed for with Neosync [1]. It was probably the hardest feature to fully solve for the customers that needed it the most, which were the ones with the most complex data sets and foreign key dependencies.
To the point where it was almost impossible to do this, at least with syncing it directly to another Postgres database with everything in tact. Meaning that if on the other side you want another pg database that has all of the same constraints, it is difficult to ensure you got the full sliced dataset. At least the way we were thinking about it.
So I figured out what I was using and created my own very paired down version of what I needed. My boot times are much faster and I’ve been totally happy with it. I also learned a lot more about shell configs as a result.
Site and blog: https://nickzelei.com Email: [email protected]