home.social

Search

28 results for “heapwolf”

  1. @heapwolf

    Hi there. I fully agree with your opinion to . While I think that the federated nature of the is still better than the siloes of that we have to endure today, it still has flaws. With P2P we can achieve more.

    I made a (still very alpha) GitHub repo called ItIsMine. It is about how to get a better system for and that allows us to and prevent any vendor or platform lock in.

    Any input very welcome!

    github.com/MarkusEicher/ItIsMi

  2. @heapwolf

    This European is. These goons of make billions but are ok with a simple TOS term to disallow as countermeasure to . You can't eat as much as you like to puke. 🤮

  3. Lol marketing people.

  4. enabled hardware is cool. Every compiler engineer should be looking at the potential for using hardware-level pointer capabilities.

  5. Is there an AI model named yet?

  6. who's writing about , or in systems programming (with under 1K followers) who i should follow?

  7. Preferisco l'architettura più antica, ma la di Berlino è straordinariamente bella.

  8. if you're using and trying to transition away from it, our professional services team is ready to help you — at no charge.

  9. About 6 months in, we uncovered so many design and reliability problems with Hyperswarm we decided to abandon it entirely and look at .

    To our surprise, it wasn’t able to handle most kinds of NAT traversal, it was a huge code base, it was extremely complex, and had no actual spec. In fact, nothing in the P2P space had a spec. We started sweating bullets. Was it all bullshit? Did no one know what they were doing?

  10. A #Sybilattack is relevant for identity and reputation systems (This falls into the consensus bucket; the main P2P buckets are Network, Storage, Compute, or Consensus).

    Not all #P2P protocols or applications need consensus, they may use modern, asynchronous cryptography like MLS to identify. So who cares about group consensus and who should be concerned with this attack vector?

  11. A is relevant for identity and reputation systems (This falls into the consensus bucket; the main P2P buckets are Network, Storage, Compute, or Consensus).

    Not all protocols or applications need consensus, they may use modern, asynchronous cryptography like MLS to identify. So who cares about group consensus and who should be concerned with this attack vector?

  12. A #Sybilattack is relevant for identity and reputation systems (This falls into the consensus bucket; the main P2P buckets are Network, Storage, Compute, or Consensus).

    Not all #P2P protocols or applications need consensus, they may use modern, asynchronous cryptography like MLS to identify. So who cares about group consensus and who should be concerned with this attack vector?

  13. A #Sybilattack is relevant for identity and reputation systems (This falls into the consensus bucket; the main P2P buckets are Network, Storage, Compute, or Consensus).

    Not all #P2P protocols or applications need consensus, they may use modern, asynchronous cryptography like MLS to identify. So who cares about group consensus and who should be concerned with this attack vector?

  14. A #Sybilattack is relevant for identity and reputation systems (This falls into the consensus bucket; the main P2P buckets are Network, Storage, Compute, or Consensus).

    Not all #P2P protocols or applications need consensus, they may use modern, asynchronous cryptography like MLS to identify. So who cares about group consensus and who should be concerned with this attack vector?

  15. > P2P does not solve MITM attack problem P2P does not solve MITM attack problem, and most existing implementations do not use out-of-band messages for the initial key exchange.

    ❌ False. Use a search engine and enter the term “Message Layer Security”. A now standard for asynchronous secure group messages — proving post compromise and perfect forward without a central system.

  16. Ah, a little . Love him or hate him; made his mark on rock... and you know what he made his mark with… 💩

    m.youtube.com/watch?v=M1ePdB2d

  17. She definitely wasn’t the female , she was the female and one of the few with as much thunder as m.youtube.com/watch?v=KZ_7Y56r

  18. is a nice language. Having interop between Swift and ++ would be neat, but with Socket Runtime we would lose out on a lot of code reuse, Windows and Linux are mostly C/C++ code bases, and our Android is mostly C++ via the , as a result there’s actually very very little ++ in the project. I’m pretty much +0 on the idea of interop.

  19. The biggest complaint people have about is the filesystem api is inconsistent.

    This is absolutely true, and sockets.sh completely replaces it.

    Our file system api should be instantly familiar to developers, it uses under the hood😎

  20. Not only that! But just on its own is absolutely useless in practice. You need a protocol that creates a usable network.

  21. The next decade wont be about configuring , optimizing , process monitoring, , , or flip flopping between monoliths and .

    It will be about optimizing protocols. It will be about developing tools for a whole new class of p2p applications.

    This is the next chapter of computing and it’s happening now as projects like sockets.sh bring the power of p2p to the average .

  22. People are sometimes afraid of ’s complexity because it’s a .

    But client-server is a many-to-one relationship, so servers are naturally bottlenecks. Scaling them quickly becomes a distributed system of shared state with complexity equal to or greater than any p2p design.

  23. wacoca.com/media/576584/ 【山口真弘の電子書籍タッチアンドトライ】ハイエンドに近い性能で実売5万円前後!8.8型の2.5K対応Androidタブレット「Headwolf Titan 1」を試す – PC Watch #android #book #books #タブレット #パソコン/タブレット/スマートフォン #レビュー #書籍 #記事集約用