home.social

#internetprotocols — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #internetprotocols, aggregated by home.social.

  1. Evert Pot: Burrow, a new Gopher client in the browser. “After building a gopher server and website, I couldn’t quite get enough of the Gopher bug, and decided to build a Gopher client in the browser. To be honest, this is actually more like a HTTP proxy for Gopher, but I might at some point turn this into a standalone client or even port it to some native platforms.” Those of y’all old enough […]

    https://rbfirehose.com/2026/04/01/evert-pot-burrow-a-new-gopher-client-in-the-browser/
  2. Evert Pot: Burrow, a new Gopher client in the browser. “After building a gopher server and website, I couldn’t quite get enough of the Gopher bug, and decided to build a Gopher client in the browser. To be honest, this is actually more like a HTTP proxy for Gopher, but I might at some point turn this into a standalone client or even port it to some native platforms.” Those of y’all old enough […]

    https://rbfirehose.com/2026/04/01/evert-pot-burrow-a-new-gopher-client-in-the-browser/
  3. Evert Pot: Burrow, a new Gopher client in the browser. “After building a gopher server and website, I couldn’t quite get enough of the Gopher bug, and decided to build a Gopher client in the browser. To be honest, this is actually more like a HTTP proxy for Gopher, but I might at some point turn this into a standalone client or even port it to some native platforms.” Those of y’all old enough […]

    https://rbfirehose.com/2026/04/01/evert-pot-burrow-a-new-gopher-client-in-the-browser/
  4. Evert Pot: Burrow, a new Gopher client in the browser. “After building a gopher server and website, I couldn’t quite get enough of the Gopher bug, and decided to build a Gopher client in the browser. To be honest, this is actually more like a HTTP proxy for Gopher, but I might at some point turn this into a standalone client or even port it to some native platforms.” Those of y’all old enough […]

    https://rbfirehose.com/2026/04/01/evert-pot-burrow-a-new-gopher-client-in-the-browser/
  5. Evert Pot: Burrow, a new Gopher client in the browser. “After building a gopher server and website, I couldn’t quite get enough of the Gopher bug, and decided to build a Gopher client in the browser. To be honest, this is actually more like a HTTP proxy for Gopher, but I might at some point turn this into a standalone client or even port it to some native platforms.” Those of y’all old enough […]

    https://rbfirehose.com/2026/04/01/evert-pot-burrow-a-new-gopher-client-in-the-browser/
  6. Spotted in my RSS feeds: human.json. “human.json is a lightweight protocol for humans to assert authorship of their site content and vouch for the humanity of others. It uses URL ownership as identity, and trust propagates through a crawlable web of vouches between sites.”

    https://rbfirehose.com/2026/03/22/human-json/
  7. Spotted in my RSS feeds: human.json. “human.json is a lightweight protocol for humans to assert authorship of their site content and vouch for the humanity of others. It uses URL ownership as identity, and trust propagates through a crawlable web of vouches between sites.”

    https://rbfirehose.com/2026/03/22/human-json/
  8. Spotted in my RSS feeds: human.json. “human.json is a lightweight protocol for humans to assert authorship of their site content and vouch for the humanity of others. It uses URL ownership as identity, and trust propagates through a crawlable web of vouches between sites.”

    https://rbfirehose.com/2026/03/22/human-json/
  9. Spotted in my RSS feeds: human.json. “human.json is a lightweight protocol for humans to assert authorship of their site content and vouch for the humanity of others. It uses URL ownership as identity, and trust propagates through a crawlable web of vouches between sites.”

    https://rbfirehose.com/2026/03/22/human-json/
  10. “A protocol does not need to encode governance explicitly in order to shape it; it shapes governance by determining which mechanisms are easy to build, which are hard, and which are effectively impossible within the constraints the architecture imposes.”

    A good read by @laurenshof on @fediversereport

    connectedplaces.online/the-pur

    #Fediverse #ActivityPub #ATProto #OpenWeb #decentralization #DigitalGovernance #InternetProtocols

  11. “A protocol does not need to encode governance explicitly in order to shape it; it shapes governance by determining which mechanisms are easy to build, which are hard, and which are effectively impossible within the constraints the architecture imposes.”

    A good read by @laurenshof on @fediversereport

    connectedplaces.online/the-pur

    #Fediverse #ActivityPub #ATProto #OpenWeb #decentralization #DigitalGovernance #InternetProtocols

  12. “A protocol does not need to encode governance explicitly in order to shape it; it shapes governance by determining which mechanisms are easy to build, which are hard, and which are effectively impossible within the constraints the architecture imposes.”

    A good read by @laurenshof on @fediversereport

    connectedplaces.online/the-pur

    #Fediverse #ActivityPub #ATProto #OpenWeb #decentralization #DigitalGovernance #InternetProtocols

  13. “A protocol does not need to encode governance explicitly in order to shape it; it shapes governance by determining which mechanisms are easy to build, which are hard, and which are effectively impossible within the constraints the architecture imposes.”

    A good read by @laurenshof on @fediversereport

    connectedplaces.online/the-pur

    #Fediverse #ActivityPub #ATProto #OpenWeb #decentralization #DigitalGovernance #InternetProtocols

  14. “A protocol does not need to encode governance explicitly in order to shape it; it shapes governance by determining which mechanisms are easy to build, which are hard, and which are effectively impossible within the constraints the architecture imposes.”

    A good read by @laurenshof on @fediversereport

    connectedplaces.online/the-pur

    #Fediverse #ActivityPub #ATProto #OpenWeb #decentralization #DigitalGovernance #InternetProtocols

  15. Ars Technica: Many Bluetooth devices with Google Fast Pair vulnerable to “WhisperPair” hack. “A team of security researchers from Belgium’s KU Leuven University has revealed a vulnerability dubbed WhisperPair that allows an attacker to hijack Fast Pair-enabled devices to spy on the owner.”

    https://rbfirehose.com/2026/01/19/ars-technica-many-bluetooth-devices-with-google-fast-pair-vulnerable-to-whisperpair-hack/
  16. Ars Technica: Many Bluetooth devices with Google Fast Pair vulnerable to “WhisperPair” hack. “A team of security researchers from Belgium’s KU Leuven University has revealed a vulnerability dubbed WhisperPair that allows an attacker to hijack Fast Pair-enabled devices to spy on the owner.”

    https://rbfirehose.com/2026/01/19/ars-technica-many-bluetooth-devices-with-google-fast-pair-vulnerable-to-whisperpair-hack/
  17. Ars Technica: Many Bluetooth devices with Google Fast Pair vulnerable to “WhisperPair” hack. “A team of security researchers from Belgium’s KU Leuven University has revealed a vulnerability dubbed WhisperPair that allows an attacker to hijack Fast Pair-enabled devices to spy on the owner.”

    https://rbfirehose.com/2026/01/19/ars-technica-many-bluetooth-devices-with-google-fast-pair-vulnerable-to-whisperpair-hack/
  18. Ars Technica: Many Bluetooth devices with Google Fast Pair vulnerable to “WhisperPair” hack. “A team of security researchers from Belgium’s KU Leuven University has revealed a vulnerability dubbed WhisperPair that allows an attacker to hijack Fast Pair-enabled devices to spy on the owner.”

    https://rbfirehose.com/2026/01/19/ars-technica-many-bluetooth-devices-with-google-fast-pair-vulnerable-to-whisperpair-hack/
  19. The Register: Gmail preparing to drop POP3 mail fetching. “Important news for Gmail power users: Google is dropping the feature whereby Gmail can collect mail from other email accounts over POP3. The company hasn’t exactly gone out of its way to call attention to this – like actually telling anybody anything.”

    https://rbfirehose.com/2026/01/11/the-register-gmail-preparing-to-drop-pop3-mail-fetching/
  20. The Register: Gmail preparing to drop POP3 mail fetching. “Important news for Gmail power users: Google is dropping the feature whereby Gmail can collect mail from other email accounts over POP3. The company hasn’t exactly gone out of its way to call attention to this – like actually telling anybody anything.”

    https://rbfirehose.com/2026/01/11/the-register-gmail-preparing-to-drop-pop3-mail-fetching/
  21. The Register: Gmail preparing to drop POP3 mail fetching. “Important news for Gmail power users: Google is dropping the feature whereby Gmail can collect mail from other email accounts over POP3. The company hasn’t exactly gone out of its way to call attention to this – like actually telling anybody anything.”

    https://rbfirehose.com/2026/01/11/the-register-gmail-preparing-to-drop-pop3-mail-fetching/
  22. The Register: Gmail preparing to drop POP3 mail fetching. “Important news for Gmail power users: Google is dropping the feature whereby Gmail can collect mail from other email accounts over POP3. The company hasn’t exactly gone out of its way to call attention to this – like actually telling anybody anything.”

    https://rbfirehose.com/2026/01/11/the-register-gmail-preparing-to-drop-pop3-mail-fetching/
  23. 🎉 #Quad9 has finally decided to retire something nobody even knew existed! 🚀 By December 2025, HTTP/1.1 will be laid to rest, and Quad9 will bravely venture into the future of internet protocols...with the speed of a sloth on a lazy Sunday. 🤦‍♂️
    quad9.net/news/blog/doh-http-1 #HTTP1.1 #Retirement #InternetProtocols #FutureOfTech #SlothSpeed #HackerNews #ngated

  24. 🎉 #Quad9 has finally decided to retire something nobody even knew existed! 🚀 By December 2025, HTTP/1.1 will be laid to rest, and Quad9 will bravely venture into the future of internet protocols...with the speed of a sloth on a lazy Sunday. 🤦‍♂️
    quad9.net/news/blog/doh-http-1 #HTTP1.1 #Retirement #InternetProtocols #FutureOfTech #SlothSpeed #HackerNews #ngated

  25. 🎉 #Quad9 has finally decided to retire something nobody even knew existed! 🚀 By December 2025, HTTP/1.1 will be laid to rest, and Quad9 will bravely venture into the future of internet protocols...with the speed of a sloth on a lazy Sunday. 🤦‍♂️
    quad9.net/news/blog/doh-http-1 #HTTP1.1 #Retirement #InternetProtocols #FutureOfTech #SlothSpeed #HackerNews #ngated

  26. 🎉 #Quad9 has finally decided to retire something nobody even knew existed! 🚀 By December 2025, HTTP/1.1 will be laid to rest, and Quad9 will bravely venture into the future of internet protocols...with the speed of a sloth on a lazy Sunday. 🤦‍♂️
    quad9.net/news/blog/doh-http-1 #HTTP1.1 #Retirement #InternetProtocols #FutureOfTech #SlothSpeed #HackerNews #ngated

  27. arstechnica.com/security/2025/

    #tracking code #Meta and Russian #Yandex embed into millions of websites is #deanonymizing #android users by abusing legitimate #Internetprotocols, causing #Chrome and other browsers to surreptitiously send #uniqueidentifiers to #nativeapps installed on their devices…#Google says it's investigating the abuse, which allows Meta and Yandex to convert ephemeral web identifiers into persistent mobile app user identities.

  28. arstechnica.com/security/2025/

    #tracking code #Meta and Russian #Yandex embed into millions of websites is #deanonymizing #android users by abusing legitimate #Internetprotocols, causing #Chrome and other browsers to surreptitiously send #uniqueidentifiers to #nativeapps installed on their devices…#Google says it's investigating the abuse, which allows Meta and Yandex to convert ephemeral web identifiers into persistent mobile app user identities.

  29. arstechnica.com/security/2025/

    #tracking code #Meta and Russian #Yandex embed into millions of websites is #deanonymizing #android users by abusing legitimate #Internetprotocols, causing #Chrome and other browsers to surreptitiously send #uniqueidentifiers to #nativeapps installed on their devices…#Google says it's investigating the abuse, which allows Meta and Yandex to convert ephemeral web identifiers into persistent mobile app user identities.

  30. arstechnica.com/security/2025/

    #tracking code #Meta and Russian #Yandex embed into millions of websites is #deanonymizing #android users by abusing legitimate #Internetprotocols, causing #Chrome and other browsers to surreptitiously send #uniqueidentifiers to #nativeapps installed on their devices…#Google says it's investigating the abuse, which allows Meta and Yandex to convert ephemeral web identifiers into persistent mobile app user identities.

  31. arstechnica.com/security/2025/

    #tracking code #Meta and Russian #Yandex embed into millions of websites is #deanonymizing #android users by abusing legitimate #Internetprotocols, causing #Chrome and other browsers to surreptitiously send #uniqueidentifiers to #nativeapps installed on their devices…#Google says it's investigating the abuse, which allows Meta and Yandex to convert ephemeral web identifiers into persistent mobile app user identities.

  32. #InternetGovernance #InternetProtocols #HumanRights #Decentralization #AntiCensorship #DataProtection: "The Internet Research Task Force has published a Request For Comments document its authors hope will mean developers of comms protocols and architectures consider the human rights implications of their efforts.

    RFC 9620 – titled "Guidelines for Human Rights Protocol and Architecture Considerations" – is merely informational. It's not a standard, nor is it on track to become one.

    It "outlines a set of human rights protocol considerations for protocol developers" and "provides questions that engineers should ask themselves when developing or improving protocols if they want to understand how their decisions can potentially influence the exercise of human rights on the internet."

    The document explains the need for its existence as follows:"

    theregister.com/2024/09/18/rfc

  33. #InternetGovernance #InternetProtocols #HumanRights #Decentralization #AntiCensorship #DataProtection: "The Internet Research Task Force has published a Request For Comments document its authors hope will mean developers of comms protocols and architectures consider the human rights implications of their efforts.

    RFC 9620 – titled "Guidelines for Human Rights Protocol and Architecture Considerations" – is merely informational. It's not a standard, nor is it on track to become one.

    It "outlines a set of human rights protocol considerations for protocol developers" and "provides questions that engineers should ask themselves when developing or improving protocols if they want to understand how their decisions can potentially influence the exercise of human rights on the internet."

    The document explains the need for its existence as follows:"

    theregister.com/2024/09/18/rfc

  34. #InternetGovernance #InternetProtocols #HumanRights #Decentralization #AntiCensorship #DataProtection: "The Internet Research Task Force has published a Request For Comments document its authors hope will mean developers of comms protocols and architectures consider the human rights implications of their efforts.

    RFC 9620 – titled "Guidelines for Human Rights Protocol and Architecture Considerations" – is merely informational. It's not a standard, nor is it on track to become one.

    It "outlines a set of human rights protocol considerations for protocol developers" and "provides questions that engineers should ask themselves when developing or improving protocols if they want to understand how their decisions can potentially influence the exercise of human rights on the internet."

    The document explains the need for its existence as follows:"

    theregister.com/2024/09/18/rfc

  35. #InternetGovernance #InternetProtocols #HumanRights #Decentralization #AntiCensorship #DataProtection: "The Internet Research Task Force has published a Request For Comments document its authors hope will mean developers of comms protocols and architectures consider the human rights implications of their efforts.

    RFC 9620 – titled "Guidelines for Human Rights Protocol and Architecture Considerations" – is merely informational. It's not a standard, nor is it on track to become one.

    It "outlines a set of human rights protocol considerations for protocol developers" and "provides questions that engineers should ask themselves when developing or improving protocols if they want to understand how their decisions can potentially influence the exercise of human rights on the internet."

    The document explains the need for its existence as follows:"

    theregister.com/2024/09/18/rfc

  36. #InternetGovernance #InternetProtocols #HumanRights #Decentralization #AntiCensorship #DataProtection: "The Internet Research Task Force has published a Request For Comments document its authors hope will mean developers of comms protocols and architectures consider the human rights implications of their efforts.

    RFC 9620 – titled "Guidelines for Human Rights Protocol and Architecture Considerations" – is merely informational. It's not a standard, nor is it on track to become one.

    It "outlines a set of human rights protocol considerations for protocol developers" and "provides questions that engineers should ask themselves when developing or improving protocols if they want to understand how their decisions can potentially influence the exercise of human rights on the internet."

    The document explains the need for its existence as follows:"

    theregister.com/2024/09/18/rfc