• 0 Posts
  • 95 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle

  • Me:

    Shows a demo function just to show how it could be done.

    Manager: (looking in his manager book)

    -“So it’s already implemented!”

    Me: no it needs to be programmed first

    Manager: but it already is, i can see it on screen!

    Me: it has to be implemented correctly.

    Manager (looking in book again)

    -“How much time if you implement quickly as quick as possible?”

    Me: it will take X time.

    Manager: Starts to call tech-lead and chief boot-licker to “convince” me it doesn’t need that much time.

    After 3 hours of painful meeting I say okay okay okay and pushes ‘best I could do’ to production in the same evening. Reinforcing the idea that I’m a lying bad programmer and that Manager, tech-lead and chief boot-licker are correct.

    Source: 10 years of gamedev




  • Thanks!

    IPFS is static, whereas tenfingers is dynamic when it comes to the links. So you can update the shared data without the need of redistributing the link.

    That said, its also very different tech wise, there is no need for benevolent nodes (or some crypto or payment).

    Nodes do not need to be trustworthy either, so node discovery is very simple (basically just ask other nodes for known nodes).

    The distribution part, where nodes share your data, is based on reciprocal sharing, you share theirs and they share yours. If they don’t share any more (there are checks) you just ditch the deal and ask for a new deal with another node.

    With over sharing (default is you share your data with 10 other nodes, sharing their data) this should both make bad nodes a no problem, but also make for good uptime and takedown safety.

    This system also makes it scalable infinitely node wise, as every node does not need to know all other nodes, just enough for their need (for example thousands out if millions of existing nodes).

    To share lots if data, you need to bring enough storage and bandwith to the table because it’s reciprocal, so basically it’s up to your node how much it can share.

    Big data sets are always complicated because of errors and long download times, I have done 300MB files without problems, but the download process sure can be made better (with parallel downloading for example and better error handling).

    I haven’t worked on sharing way bigger datasets, even a simple terabyte is a pita to download on the regular internet :-) and the use case is more the idea of sharing lots of smaller data, like a website for example, or a chat.

    What do you think, am I missing something important? Or of course if you have other questions please do ask!

    Also, sorry I’m writing this on my mobile so it’s not very well written.

    Edit: missed one question; getting the data is straight forward to use (a bit complicated how it’s handled because of the changing nature of things) but when you download, you have the addresses of the nodes sharing your data so you just connect to one of them and download it (or the next if the first one isn’t up etc and so on). So that should not be any kind of bottleneck.











  • I hate induction with a passion, beep boop it doesn’t work because a drop of water, you can’t put anything on it, the controls are obnoxious and you have to change at least some cookwear.

    I love gas, sure it’s more a preference than logic but it’s so snappy ! Turn the button and you have 5000watts of heat, no long click this, short click that, and when done, just turn the knob.

    Now, it has drawbacks like when it’s windy, it does get super hot etc. but I’d get hologen (with knobs) before any induction.

    /Rant off