1. 2

    Shameless plug: All the companies(Google, Microsoft…) are telling trust us. But, I believe that we should trust us instead of relying on third parties. They always change when businesses interest changes. This is where web3 is coming to play. Technologies like IFFS, safe network are coming. Looking at the scale issue, I guess this web3 takes at least 5 more years. But, this kind p2p technology is possible with small-scaled mesh. Mesh networks within our devices or families. From the beginning, I hate the idea of storing passwords in the third-party password manager. Later, I fell into the same trap because a managing lot of passwords is difficult. So, I building an open-source p2p password manger. Replicates the passwords within your devices, instead of storing everything at the vendor’s cloud. It’s half-way for the closed beta release. I would like to hear everyone’s feedback on this idea.

    Thanks

    1. 1

      Replicates the passwords within your devices, instead of storing everything at the vendor’s cloud. It’s half-way for the closed beta release. I would like to hear everyone’s feedback on this idea.

      We need more of this kind of thing! Telling people not to store their shit “in the cloud” is only half the story. We also need easy to use(!) alternatives we can point to when they ask “so how should I do it?”

    1. 3

      The asciinema is next to useless, you spend half the time booting kubectl. I still don’t now what this software is doing.

      1. 1

        Hey, Sorry for the useless asciinema.

        I actually created pathivu in the cluster and used katchi to see all the logs from the pathivu.

        The end result will look like this https://github.com/pathivu/pathivu#use-katchi-to-see-logs

        I’ll update the asciinema soon.

      1. 2

        Great!

        Is there a design overview or a comparison with, say, loki?

        1. 2

          loki doesn’t do indexing. Here we do indexing. When it comes to design, it just append only log like Kafka. The main reason to write in rust for the memory handling. In go-lang, folks already facing lot memory-related issues. Personally, I haven’t benchmarked Loki in big deployment. I hope, there is lot of rooms in Pathivu for optimization, I released it in MVP state to get feedback from the community, whether folks would love Pathipu or not. So far, I heard good about pathipu. Got a lot of motivation to build further. <3

          1. 2

            How does it do compacting? And are there already ideas regarding HA? Does it index after simple word splitting or is it doing anything fancy?

            It is great having a different tool. Loki in HA is pretty involved and all the elasticsearch options are an operational nightmare. It was most unfortunate that oklog died. It’s great having something simpler and written with efficiency in mind.

            1. 2

              Now, it won’t do any compaction. Regarding HA, planning to make it multi-node. currently, it’s a single node.

              Indexing is simple splitting and stop word cleaning. If the user demands something fancy, I will implement.

              The main idea for me to build this is to efficient and cost-saving.

              In my previous company, there was a saying “Reducing AWS cost itself a buissness”

              1. 1

                Thank you for answering. Have you looked at the loki-grafana protocol? It would be great to use grafana for looking at the logs. That way, one does not have to train users to use a different tool.

                1. 2

                  grafana plugin is in the pipeline. Folks can see in a week.

        1. 2

          What do you mean by “high rate” and “at scale?”

          Do you have any interesting benchmarks?

          1. 1

            I’m able to make 10mb/s. But, lot of optimization yet to made. eg. multi-thread ingester…

            Once it comes to right shape, will post it in readme.

            If you’re interested, I would like to share my benchmark script with you.