Hacker Newsnew | past | comments | ask | show | jobs | submit | dpc_01234's commentslogin

P2P? I have a p2p social network with a public/demo instance hosted at https://rostra.me .

I wish I had your problems. :D . Problems that are really only a mild inconvenience, and can be solved with a single line in hosts file.

My biggest and possibly only problem preventing me from going IPV6-only is that Github doesn't support it, and there's just too much darn software I need to needs Github. (Yes, I know NAT64 exist - it's just extra complexity for something that is not even my problem in the first place).


This encoding is so long, that I'm more likely to remember the raw address. :D

And I don't think I ever typed manually any IPv6 address other than `::1`.


No need to type `::1` anymore, you can instead just type `The new times take now beneath the new time while new times take the new year.`

OK. That's much easier. :D

You can make unique local address subnets with simple addresses.

I use a simple one like `fd10::1/128` and `fd10::2/128` and so on

Technically speaking RFC 4193 says you should use random bits. But I don't care.


These ad companies pay for transfer too.

Install AdNauseam if you have unmetered connection and let it download as much data from them as it can.


TL;DR: Generic uninspired anti-Wayland rant.


> In my experience, the most natural way to write things in Rust is usually the fastest (or close enough) as well.

Well, a lot of C/Odin/Zig people will point out that Rust's stdlib encourages heap allocations. For actually best performance you typically want to store your data in some data-oriented data model, avoid allocations and so on, which is not exactly against idiomatic Rust, but more than just a typical straighforward Rust just throwing allocations around.


Fair point, I don't tend to do much with heap in Rust (or any language) as I do hard realtime. You allocate all you will need up front.

As for data oriented design: yes, and it depends on your usage pattern. E.g. arrays of structs can still be better than struct of arrays if that matches your cache line access pattern. Zig probably makes SOA easier for the cases where that is more efficient (I haven't used Zig, but I have read a bit about it. It has some cool ideas (comptime), but also things I can't get behind such as lack of RAII, and generally lack of memory safety.)


It's slop derangement syndrome. Agreed.


Joke's on you — All my posts are written by some Slopus now.


No idea what happened, but you'd be a fool to believe anything BBC says.


why?


Because the BBC has been shown to be heavily biased towards the 'metropolitan' and 'liberal' sides - where London goes, so does the BBC. Trusting the BBC on its word is just as unwise as trusting e.g. NPR/PBS or CNN/MSNBC/FOX (USA), ARD/ZDF/NDR (Germany), NOS (Netherlands) or SVT/SR (Sweden). In short, trusting any of the media - whether legacy or new - on their word is unwise, verification is needed. Unfortunately it is getting harder to trust verification videos as well since the advent of generative AV-models.

If this is commonplace as the BBC claims it should be possible for other outlets to find more soldiers - in Ukraine or in Russia - who are willing to share these stories. If only Russia had independent media - https://novayagazeta.ru/ claims to be independent, maybe it is and maybe it is not but I find it hard to believe that an organisation which is housed at 101000, Moscow, Potapovsky lane, 3, building 1 (address taken from the footer of their page) can remain independent for long - it would be something for Russian media to pick up.


It's easier than ever to build p2p software. E.g. You can use Pkarr as a distributed identity system, and Iroh for reliable p2p connectivity.

There's no point in messing with custom hardware, etc. We could host bunch of redundant p2p access points for everyone, and use p2p portable software for everything.

E.g. I'm building a P2P/F2F Social Media protocol that is very close to syndication platform. https://app.radicle.xyz/nodes/radicle.dpc.pw/rad:zzK566qFsZn... . I'm not saying that it's exactly the same thing as author is looking for, but the technical bits and even functionality are very close.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: