Prithvi Shahi

@fjl Thanks that's fair to go in the same direction as the eth consensus specification i.e. only utilizing TCP. However, I strongly advocate for enabling at least QUIC in addition...

@fjl Are you open to having a short design/architecture meeting, sometime next week (friendly to your timezone - CEST?), with Go & Rust libp2p maintainers? I will post the discussion...

sweet, I sent an invite to the email address listed on your GH profile.

Here are the meeting notes from 2023-01-25 https://pl-strflt.notion.site/2023-01-25-devp2p-libp2p-minutes-692a4068d60a4781877c34839100764b

@lidel @reidw Please add me to meeting too

@luc-mercier this is still the case right? Has there been any new conclusion not captured here: https://docs.google.com/document/d/13GCGj5SaUe7JhgiMmiW7GSIzejtQ4c1uohJFY89tobc/edit# (is pre_upgrade still banned in NNS and should it be banned here too)

> Has this been debugged and resolved? We noticed that a lot last week when working on the identity provider, and it almost derailed our Dom demo… > (My gut...

1st draft: https://hackmd.io/@F8NONPbbRv-IVOAPB7tKPw/SyQeJn8Nh

@TheDiscordian how are things going on this front?

@DougAnderson444 I created this issue: https://github.com/libp2p/universal-connectivity/issues/64 thanks for the reminder. > Should we add the Browser's multiaddress to the frontend UI somewhere, so we can "add Browser Peer"? Right now...