nanog mailing list archives
Re: Parler
From: sronan () ronan-online com
Date: Sun, 10 Jan 2021 17:42:41 -0500
No, this is a list for Network Operators. Sent from my iPhone
On Jan 10, 2021, at 5:32 PM, K. Scott Helms <kscott.helms () gmail com> wrote: This is a list for pushing bits. The fact that many/most of us have other businesses doesn't make this an appropriate forum for SIP issues (to use my own work as an example).On Sun, Jan 10, 2021, 4:52 PM <sronan () ronan-online com> wrote: This is a list for Network Operators, AWS certainly operates networks. Sent from my iPhoneOn Jan 10, 2021, at 4:27 PM, K. Scott Helms <kscott.helms () gmail com> wrote: No, It really does not. Section 230 only applies to publishers, and not to network providers. If this were a cloud hosting provider list then you'd be correct, but as a network provider's list it does not belong here. Scott HelmsOn Sun, Jan 10, 2021 at 3:21 PM Lady Benjamin PD Cannon <ben () 6by7 net> wrote: As network operations and compute/cloud/hosting operations continue to coalesce, I very much disagree with you. Section 230 is absolutely relevant, this discussion is timely and relevant, and it directly affects me as both a telecom and cloud compute/services provider. —L.B. Lady Benjamin PD Cannon, ASCE 6x7 Networks & 6x7 Telecom, LLC CEO ben () 6by7 net "The only fully end-to-end encrypted global telecommunications company in the world.” FCC License KJ6FJJ <Speedtest9118.png> <Ben LIC.png>On Jan 10, 2021, at 12:13 PM, K. Scott Helms <kscott.helms () gmail com> wrote: It's not, and frankly it's disappointing to see people pushing an agenda here. Scott HelmsOn Sun, Jan 10, 2021 at 9:37 AM <sronan () ronan-online com> wrote: NANOG is a group of Operators, discussion does not have to be about networking. I have already explained how this represents a significant issue for Network Operators. On Jan 10, 2021, at 9:09 AM, Mike Bolitho <mikebolitho () gmail com> wrote: It has nothing to do with networking. Their decision was necessarily political. If you can specifically bring up an issue, beyond speculative, on how their new chosen CDN is somehow now causing congestion or routing issues on the public internet, then great. But as of now, that isn't even a thing. It's just best to leave it alone because it will devolve into chaos. - Mike BolithoOn Sun, Jan 10, 2021, 6:54 AM <sronan () ronan-online com> wrote: Why? This is extremely relevant to network operators and is not political at all. On Jan 10, 2021, at 8:51 AM, Mike Bolitho <mikebolitho () gmail com> wrote: Can we please not go down this rabbit hole on here? List admins? - Mike BolithoOn Sun, Jan 10, 2021, 1:26 AM William Herrin <bill () herrin us> wrote: Anybody looking for a new customer opportunity? It seems Parler is in search of a new service provider. Vendors need only provide all the proprietary AWS APIs that Parler depends upon to function. https://www.washingtonpost.com/technology/2021/01/09/amazon-parler-suspension/ Regards, Bill HErrin
Current thread:
- Re: Parler, (continued)
- Re: Parler William Herrin (Jan 17)
- DDOS-Guard [was: Parler] Rich Kulawiec (Jan 21)
- RE: DDOS-Guard [was: Parler] Jean St-Laurent via NANOG (Jan 29)
- Re: Parler William Herrin (Jan 17)
- Re: Parler Eric Kuhnke (Jan 18)
- Re: Parler Masataka Ohta (Jan 19)
- Re: Parler sronan (Jan 10)
- Re: Parler David Bass (Jan 10)
- Re: Parler Jim Mercer (Jan 10)
- Re: Parler sronan (Jan 10)
- Re: Parler K. Scott Helms (Jan 10)
- Re: Parler sronan (Jan 10)
- Re: Parler K. Scott Helms (Jan 10)
- Re: Parler mark seery (Jan 10)
- Re: Parler K. Scott Helms (Jan 11)
- RE: Parler Kevin McCormick (Jan 12)
- Re: Parler Paul Timmins (Jan 12)
- Re: Parler Andy Ringsmuth (Jan 12)
- Re: Parler John Curran (Jan 12)
- Re: Parler Seth Mattinen (Jan 12)
- Re: Parler Bryan Holloway (Jan 13)
- Re: Parler Joe Provo (Jan 14)
- Re: Parler K. Scott Helms (Jan 10)