A small tool to view real-world ActivityPub objects as JSON! Enter a URL
or username from Mastodon or a similar service below, and we'll send a
request with
the right
Accept
header
to the server to view the underlying object.
{
"@context": [
"https://www.w3.org/ns/activitystreams",
"https://udongein.xyz/schemas/litepub-0.1.jsonld",
{
"@language": "und"
}
],
"actor": "https://udongein.xyz/users/lispi314",
"attachment": [],
"attributedTo": "https://udongein.xyz/users/lispi314",
"cc": [
"https://www.w3.org/ns/activitystreams#Public"
],
"content": "<p><span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AQE53XWKOvypmRJzXs\" href=\"https://mstdn.social/@kkarhan\" rel=\"ugc\">@<span>kkarhan</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AYfSrxFDQ5s0RwDM3M\" href=\"https://mstdn.social/@PiTau\" rel=\"ugc\">@<span>PiTau</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AOwPEzuqWnt1ofIdzU\" href=\"https://mstdn.social/@rysiek\" rel=\"ugc\">@<span>rysiek</span></a></span> He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.</p><p>Also, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a <em>lot</em> of unix-brained regression that needs to be addressed before blaming any other party.</p><p>(And Microsoft dropped <a href=\"https://en.wikipedia.org/wiki/Singularity_(operating_system)\">the last hope for common & good sense to prevail in their ecosystem</a> back in 2015 so that's the end of the line for them too.)</p><p>We're <em>still</em> writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, <a href=\"https://learn.adacore.com/courses/Ada_For_The_Embedded_C_Developer/index.html\">even in embedded spaces</a>.</p><p>The entire mobile ecosystem has been nothing but an avoidable disaster made-up of bad decisions from the start.</p><p>The realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. <a href=\"https://geti2p.net/en/\">I2P</a> is <a href=\"https://geti2p.net/en/about/intro\">20 years old</a>. And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a <strong>lot</strong> of countries.</p><p>And right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general <em>completely</em> ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent/agnostic <a href=\"https://www.complete.org/asynchronous-communication/\">Asynchronous Communication</a> is a basic requirement and <a href=\"https://www.complete.org/recovering-our-lost-free-will-online-tools-and-techniques-that-are-available-now/\">paradigm to build around</a>, because infrastructure capable of lending itself to low-latency communication <a href=\"https://www.complete.org/tools-for-communicating-offline-and-in-difficult-circumstances/\">cannot be meaningfully assumed anywhere</a>.</p><p>(By the way, neither <a href=\"https://en.wikipedia.org/wiki/FidoNet\">Fidonet</a> nor <a href=\"https://en.wikipedia.org/wiki/Usenet\">Usenet</a> made such <a href=\"https://mastodon.top/users/lispi314/statuses/111253066257920146\">assumptions about infrastructure</a>. We've regressed a lot.)</p><p>We've also had ample time to observe that centralized infrastructures are basically optimized for easy takedowns, and yet the majority of current systems are still neither distributed nor P2P.</p><p>So yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.</p>",
"context": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"conversation": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"formerRepresentations": {
"orderedItems": [
{
"actor": "https://udongein.xyz/users/lispi314",
"attachment": [],
"attributedTo": "https://udongein.xyz/users/lispi314",
"cc": [
"https://www.w3.org/ns/activitystreams#Public"
],
"content": "<p><span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AQE53XWKOvypmRJzXs\" href=\"https://mstdn.social/@kkarhan\" rel=\"ugc\">@<span>kkarhan</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AYfSrxFDQ5s0RwDM3M\" href=\"https://mstdn.social/@PiTau\" rel=\"ugc\">@<span>PiTau</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AOwPEzuqWnt1ofIdzU\" href=\"https://mstdn.social/@rysiek\" rel=\"ugc\">@<span>rysiek</span></a></span> He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.</p><p>Also, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a <em>lot</em> of unix-brained regression that needs to be addressed before blaming any other party.</p><p>(And Microsoft dropped <a href=\"https://en.wikipedia.org/wiki/Singularity_(operating_system)\">the last hope for common & good sense to prevail in their ecosystem</a> back in 2015 so that's the end of the line for them too.)</p><p>We're <em>still</em> writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, even in embedded spaces.</p><p>The entire mobile ecosystem has been nothing but an avoidable disaster made-up of bad decisions from the start.</p><p>The realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. <a href=\"https://geti2p.net/en/\">I2P</a> is <a href=\"https://geti2p.net/en/about/intro\">20 years old</a>. And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a <strong>lot</strong> of countries.</p><p>And right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general <em>completely</em> ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent/agnostic <a href=\"https://www.complete.org/asynchronous-communication/\">Asynchronous Communication</a> is a basic requirement and <a href=\"https://www.complete.org/recovering-our-lost-free-will-online-tools-and-techniques-that-are-available-now/\">paradigm to build around</a>, because infrastructure capable of lending itself to low-latency communication <a href=\"https://www.complete.org/tools-for-communicating-offline-and-in-difficult-circumstances/\">cannot be meaningfully assumed anywhere</a>.</p><p>(By the way, neither <a href=\"https://en.wikipedia.org/wiki/FidoNet\">Fidonet</a> nor <a href=\"https://en.wikipedia.org/wiki/Usenet\">Usenet</a> made such <a href=\"https://mastodon.top/users/lispi314/statuses/111253066257920146\">assumptions about infrastructure</a>. We've regressed a lot.)</p><p>We've also had ample time to observe that centralized infrastructures are basically optimized for easy takedowns, and yet the majority of current systems are still neither distributed nor P2P.</p><p>So yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.</p>",
"context": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"conversation": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"inReplyTo": "https://mstdn.social/users/kkarhan/statuses/111378100236269307",
"published": "2023-11-09T03:47:51.433755Z",
"source": {
"content": "@kkarhan@mstdn.social @PiTau@mstdn.social @rysiek@mstdn.social He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.\r\n\r\nAlso, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a *lot* of unix-brained regression that needs to be addressed before blaming any other party.\r\n\r\n(And Microsoft dropped [the last hope for common & good sense to prevail in their ecosystem](https://en.wikipedia.org/wiki/Singularity_(operating_system)) back in 2015 so that's the end of the line for them too.)\r\n\r\nWe're *still* writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, even in embedded spaces.\r\n\r\nThe entire mobile ecosystem has been nothing but an avoidable disaster made-up of bad decisions from the start.\r\n\r\nThe realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. [I2P](https://geti2p.net/en/) is [20 years old](https://geti2p.net/en/about/intro). And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a **lot** of countries.\r\n\r\nAnd right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general *completely* ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent/agnostic [Asynchronous Communication](https://www.complete.org/asynchronous-communication/) is a basic requirement and [paradigm to build around](https://www.complete.org/recovering-our-lost-free-will-online-tools-and-techniques-that-are-available-now/), because infrastructure capable of lending itself to low-latency communication [cannot be meaningfully assumed anywhere](https://www.complete.org/tools-for-communicating-offline-and-in-difficult-circumstances/).\r\n\r\n(By the way, neither [Fidonet](https://en.wikipedia.org/wiki/FidoNet) nor [Usenet](https://en.wikipedia.org/wiki/Usenet) made such [assumptions about infrastructure](https://mastodon.top/users/lispi314/statuses/111253066257920146). We've regressed a lot.)\r\n\r\nWe've also had ample time to observe that centralized infrastructures are basically optimized for easy takedowns, and yet the majority of current systems are still neither distributed nor P2P.\r\n\r\nSo yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.",
"mediaType": "text/markdown"
},
"summary": "",
"tag": [
{
"href": "https://mstdn.social/users/kkarhan",
"name": "@kkarhan@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/PiTau",
"name": "@PiTau@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/rysiek",
"name": "@rysiek@mstdn.social",
"type": "Mention"
}
],
"to": [
"https://mstdn.social/users/kkarhan",
"https://udongein.xyz/users/lispi314/followers",
"https://mstdn.social/users/PiTau",
"https://mstdn.social/users/rysiek"
],
"type": "Note",
"updated": "2023-11-09T04:16:33.588297Z"
},
{
"actor": "https://udongein.xyz/users/lispi314",
"attachment": [],
"attributedTo": "https://udongein.xyz/users/lispi314",
"cc": [
"https://www.w3.org/ns/activitystreams#Public"
],
"content": "<p><span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AQE53XWKOvypmRJzXs\" href=\"https://mstdn.social/@kkarhan\" rel=\"ugc\">@<span>kkarhan</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AYfSrxFDQ5s0RwDM3M\" href=\"https://mstdn.social/@PiTau\" rel=\"ugc\">@<span>PiTau</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AOwPEzuqWnt1ofIdzU\" href=\"https://mstdn.social/@rysiek\" rel=\"ugc\">@<span>rysiek</span></a></span> He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.</p><p>Also, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a <em>lot</em> of unix-brained regression that needs to be addressed before blaming any other party.</p><p>(And Microsoft dropped <a href=\"https://en.wikipedia.org/wiki/Singularity_(operating_system)\">the last hope for common & good sense to prevail in their ecosystem</a> back in 2015 so that's the end of the line for them too.)</p><p>We're <em>still</em> writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, even in embedded spaces.</p><p>The entire mobile ecosystem has been nothing but an avoidable disaster made-up of bad decisions from the start.</p><p>The realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. <a href=\"https://geti2p.net/en/\">I2P</a> is <a href=\"https://geti2p.net/en/about/intro\">20 years old</a>. And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a <strong>lot</strong> of countries.</p><p>And right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general <em>completely</em> ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent/agnostic <a href=\"https://www.complete.org/asynchronous-communication/\">Asynchronous Communication</a> is a basic requirement and <a href=\"https://www.complete.org/recovering-our-lost-free-will-online-tools-and-techniques-that-are-available-now/\">paradigm to build around</a>, because infrastructure capable of lending itself to low-latency communication <a href=\"https://www.complete.org/tools-for-communicating-offline-and-in-difficult-circumstances/\">cannot be meaningfully assumed anywhere</a>.</p><p>(By the way, neither <a href=\"https://en.wikipedia.org/wiki/FidoNet\">Fidonet</a> nor <a href=\"https://en.wikipedia.org/wiki/Usenet\">Usenet</a> made such <a href=\"https://mastodon.top/@lispi314/111253066257920146\">assumptions about infrastructure</a>. We've regressed a lot.)</p><p>We've also had ample time to observe that centralized infrastructures are basically optimized for easy takedowns, and yet the majority of current systems are still neither distributed nor P2P.</p><p>So yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.</p>",
"context": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"conversation": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"inReplyTo": "https://mstdn.social/users/kkarhan/statuses/111378100236269307",
"published": "2023-11-09T03:47:51.433755Z",
"source": {
"content": "@kkarhan@mstdn.social @PiTau@mstdn.social @rysiek@mstdn.social He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.\r\n\r\nAlso, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a *lot* of unix-brained regression that needs to be addressed before blaming any other party.\r\n\r\n(And Microsoft dropped [the last hope for common & good sense to prevail in their ecosystem](https://en.wikipedia.org/wiki/Singularity_(operating_system)) back in 2015 so that's the end of the line for them too.)\r\n\r\nWe're *still* writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, even in embedded spaces.\r\n\r\nThe entire mobile ecosystem has been nothing but an avoidable disaster made-up of bad decisions from the start.\r\n\r\nThe realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. [I2P](https://geti2p.net/en/) is [20 years old](https://geti2p.net/en/about/intro). And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a **lot** of countries.\r\n\r\nAnd right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general *completely* ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent/agnostic [Asynchronous Communication](https://www.complete.org/asynchronous-communication/) is a basic requirement and [paradigm to build around](https://www.complete.org/recovering-our-lost-free-will-online-tools-and-techniques-that-are-available-now/), because infrastructure capable of lending itself to low-latency communication [cannot be meaningfully assumed anywhere](https://www.complete.org/tools-for-communicating-offline-and-in-difficult-circumstances/).\r\n\r\n(By the way, neither [Fidonet](https://en.wikipedia.org/wiki/FidoNet) nor [Usenet](https://en.wikipedia.org/wiki/Usenet) made such [assumptions about infrastructure](https://mastodon.top/@lispi314/111253066257920146). We've regressed a lot.)\r\n\r\nWe've also had ample time to observe that centralized infrastructures are basically optimized for easy takedowns, and yet the majority of current systems are still neither distributed nor P2P.\r\n\r\nSo yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.",
"mediaType": "text/markdown"
},
"summary": "",
"tag": [
{
"href": "https://mstdn.social/users/kkarhan",
"name": "@kkarhan@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/PiTau",
"name": "@PiTau@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/rysiek",
"name": "@rysiek@mstdn.social",
"type": "Mention"
}
],
"to": [
"https://mstdn.social/users/kkarhan",
"https://udongein.xyz/users/lispi314/followers",
"https://mstdn.social/users/PiTau",
"https://mstdn.social/users/rysiek"
],
"type": "Note",
"updated": "2023-11-09T04:13:47.127197Z"
},
{
"actor": "https://udongein.xyz/users/lispi314",
"attachment": [],
"attributedTo": "https://udongein.xyz/users/lispi314",
"cc": [
"https://www.w3.org/ns/activitystreams#Public"
],
"content": "<p><span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AQE53XWKOvypmRJzXs\" href=\"https://mstdn.social/@kkarhan\" rel=\"ugc\">@<span>kkarhan</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AYfSrxFDQ5s0RwDM3M\" href=\"https://mstdn.social/@PiTau\" rel=\"ugc\">@<span>PiTau</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AOwPEzuqWnt1ofIdzU\" href=\"https://mstdn.social/@rysiek\" rel=\"ugc\">@<span>rysiek</span></a></span> He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.</p><p>Also, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a <em>lot</em> of unix-brained regression that needs to be addressed before blaming any other party.</p><p>(And Microsoft dropped <a href=\"https://en.wikipedia.org/wiki/Singularity_(operating_system)\">the last hope for common & good sense to prevail in their ecosystem</a> back in 2015 so that's the end of the line for them too.)</p><p>We're <em>still</em> writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, even in embedded spaces.</p><p>The entire mobile ecosystem has been nothing but an avoidable disaster made-up of bad decisions from the start.</p><p>The realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. <a href=\"https://geti2p.net/en/\">I2P</a> is <a href=\"https://geti2p.net/en/about/intro\">20 years old</a>. And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a <strong>lot</strong> of countries.</p><p>And right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general <em>completely</em> ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent/agnostic <a href=\"https://www.complete.org/asynchronous-communication/\">Asynchronous Communication</a> is a basic requirement and <a href=\"https://www.complete.org/recovering-our-lost-free-will-online-tools-and-techniques-that-are-available-now/\">paradigm to build around</a>, because infrastructure capable of lending itself to low-latency communication <a href=\"https://www.complete.org/tools-for-communicating-offline-and-in-difficult-circumstances/\">cannot be meaningfully assumed anywhere</a>.</p><p>We've also had ample time to observe that centralized infrastructures are basically optimized for easy takedowns, and yet the majority of current systems are still neither distributed nor P2P.</p><p>So yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.</p>",
"context": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"conversation": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"inReplyTo": "https://mstdn.social/users/kkarhan/statuses/111378100236269307",
"published": "2023-11-09T03:47:51.433755Z",
"source": {
"content": "@kkarhan@mstdn.social @PiTau@mstdn.social @rysiek@mstdn.social He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.\r\n\r\nAlso, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a *lot* of unix-brained regression that needs to be addressed before blaming any other party.\r\n\r\n(And Microsoft dropped [the last hope for common & good sense to prevail in their ecosystem](https://en.wikipedia.org/wiki/Singularity_(operating_system)) back in 2015 so that's the end of the line for them too.)\r\n\r\nWe're *still* writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, even in embedded spaces.\r\n\r\nThe entire mobile ecosystem has been nothing but an avoidable disaster made-up of bad decisions from the start.\r\n\r\nThe realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. [I2P](https://geti2p.net/en/) is [20 years old](https://geti2p.net/en/about/intro). And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a **lot** of countries.\r\n\r\nAnd right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general *completely* ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent/agnostic [Asynchronous Communication](https://www.complete.org/asynchronous-communication/) is a basic requirement and [paradigm to build around](https://www.complete.org/recovering-our-lost-free-will-online-tools-and-techniques-that-are-available-now/), because infrastructure capable of lending itself to low-latency communication [cannot be meaningfully assumed anywhere](https://www.complete.org/tools-for-communicating-offline-and-in-difficult-circumstances/).\r\n\r\nWe've also had ample time to observe that centralized infrastructures are basically optimized for easy takedowns, and yet the majority of current systems are still neither distributed nor P2P.\r\n\r\nSo yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.",
"mediaType": "text/markdown"
},
"summary": "",
"tag": [
{
"href": "https://mstdn.social/users/kkarhan",
"name": "@kkarhan@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/PiTau",
"name": "@PiTau@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/rysiek",
"name": "@rysiek@mstdn.social",
"type": "Mention"
}
],
"to": [
"https://mstdn.social/users/kkarhan",
"https://udongein.xyz/users/lispi314/followers",
"https://mstdn.social/users/PiTau",
"https://mstdn.social/users/rysiek"
],
"type": "Note",
"updated": "2023-11-09T04:05:15.192750Z"
},
{
"actor": "https://udongein.xyz/users/lispi314",
"attachment": [],
"attributedTo": "https://udongein.xyz/users/lispi314",
"cc": [
"https://www.w3.org/ns/activitystreams#Public"
],
"content": "<p><span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AQE53XWKOvypmRJzXs\" href=\"https://mstdn.social/@kkarhan\" rel=\"ugc\">@<span>kkarhan</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AYfSrxFDQ5s0RwDM3M\" href=\"https://mstdn.social/@PiTau\" rel=\"ugc\">@<span>PiTau</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AOwPEzuqWnt1ofIdzU\" href=\"https://mstdn.social/@rysiek\" rel=\"ugc\">@<span>rysiek</span></a></span> He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.</p><p>Also, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a <em>lot</em> of unix-brained regression that needs to be addressed before blaming any other party.</p><p>(And Microsoft dropped <a href=\"https://en.wikipedia.org/wiki/Singularity_(operating_system)\">the last hope for common & good sense to prevail in their ecosystem</a> back in 2015 so that's the end of the line for them too.)</p><p>We're <em>still</em> writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, even in embedded spaces.</p><p>The entire mobile ecosystem has been nothing but an avoidable disaster made-up of bad decisions from the start.</p><p>The realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. <a href=\"https://geti2p.net/en/\">I2P</a> is <a href=\"https://geti2p.net/en/about/intro\">20 years old</a>. And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a <strong>lot</strong> of countries.</p><p>And right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general <em>completely</em> ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent/agnostic <a href=\"https://www.complete.org/asynchronous-communication/\">Asynchronous Communication</a> is a basic requirement and <a href=\"https://www.complete.org/recovering-our-lost-free-will-online-tools-and-techniques-that-are-available-now/\">paradigm to build around</a>, because infrastructure capable of lending itself to low-latency communication <a href=\"https://www.complete.org/tools-for-communicating-offline-and-in-difficult-circumstances/\">cannot be meaningfully assumed anywhere</a>).</p><p>We've also had ample time to observe that centralized infrastructures are basically optimized for easy takedowns, and yet the majority of current systems are still neither distributed nor P2P.</p><p>So yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.</p>",
"context": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"conversation": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"inReplyTo": "https://mstdn.social/users/kkarhan/statuses/111378100236269307",
"published": "2023-11-09T03:47:51.433755Z",
"source": {
"content": "@kkarhan@mstdn.social @PiTau@mstdn.social @rysiek@mstdn.social He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.\r\n\r\nAlso, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a *lot* of unix-brained regression that needs to be addressed before blaming any other party.\r\n\r\n(And Microsoft dropped [the last hope for common & good sense to prevail in their ecosystem](https://en.wikipedia.org/wiki/Singularity_(operating_system)) back in 2015 so that's the end of the line for them too.)\r\n\r\nWe're *still* writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, even in embedded spaces.\r\n\r\nThe entire mobile ecosystem has been nothing but an avoidable disaster made-up of bad decisions from the start.\r\n\r\nThe realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. [I2P](https://geti2p.net/en/) is [20 years old](https://geti2p.net/en/about/intro). And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a **lot** of countries.\r\n\r\nAnd right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general *completely* ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent/agnostic [Asynchronous Communication](https://www.complete.org/asynchronous-communication/) is a basic requirement and [paradigm to build around](https://www.complete.org/recovering-our-lost-free-will-online-tools-and-techniques-that-are-available-now/), because infrastructure capable of lending itself to low-latency communication [cannot be meaningfully assumed anywhere](https://www.complete.org/tools-for-communicating-offline-and-in-difficult-circumstances/)).\r\n\r\nWe've also had ample time to observe that centralized infrastructures are basically optimized for easy takedowns, and yet the majority of current systems are still neither distributed nor P2P.\r\n\r\nSo yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.",
"mediaType": "text/markdown"
},
"summary": "",
"tag": [
{
"href": "https://mstdn.social/users/kkarhan",
"name": "@kkarhan@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/PiTau",
"name": "@PiTau@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/rysiek",
"name": "@rysiek@mstdn.social",
"type": "Mention"
}
],
"to": [
"https://mstdn.social/users/kkarhan",
"https://udongein.xyz/users/lispi314/followers",
"https://mstdn.social/users/PiTau",
"https://mstdn.social/users/rysiek"
],
"type": "Note",
"updated": "2023-11-09T04:03:17.407522Z"
},
{
"actor": "https://udongein.xyz/users/lispi314",
"attachment": [],
"attributedTo": "https://udongein.xyz/users/lispi314",
"cc": [
"https://www.w3.org/ns/activitystreams#Public"
],
"content": "<span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AQE53XWKOvypmRJzXs\" href=\"https://mstdn.social/@kkarhan\" rel=\"ugc\">@<span>kkarhan</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AYfSrxFDQ5s0RwDM3M\" href=\"https://mstdn.social/@PiTau\" rel=\"ugc\">@<span>PiTau</span></a></span> <span class=\"h-card\"><a class=\"u-url mention\" data-user=\"AOwPEzuqWnt1ofIdzU\" href=\"https://mstdn.social/@rysiek\" rel=\"ugc\">@<span>rysiek</span></a></span> He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.<br><br>Also, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a *lot* of unix-brained regression that needs to be addressed before blaming any other party.<br><br>(And Microsoft dropped the last hope for common & good sense to prevail in their ecosystem back in 2015 so that's the end of the line for them too.)<br><br>We're *still* writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, even in embedded spaces.<br><br>The entire mobile ecosystem has been nothing but an avoidable disaster of bad decisions from the start.<br><br>The realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. I2P is 20 years old. And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a /lot/ of countries.<br><br>And right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general *completely* ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent Asynchronous Communication is a basic requirement and paradigm to build around, because infrastructure capable of lending itself to low-latency communication cannot be meaningfully assumed anywhere.<br><br>So yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.",
"context": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"conversation": "tag:mstdn.social,2023-11-08:objectId=289407843:objectType=Conversation",
"inReplyTo": "https://mstdn.social/users/kkarhan/statuses/111378100236269307",
"published": "2023-11-09T03:47:51.433755Z",
"sensitive": false,
"source": {
"content": "@kkarhan@mstdn.social @PiTau@mstdn.social @rysiek@mstdn.social He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.\n\nAlso, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a *lot* of unix-brained regression that needs to be addressed before blaming any other party.\n\n(And Microsoft dropped the last hope for common & good sense to prevail in their ecosystem back in 2015 so that's the end of the line for them too.)\n\nWe're *still* writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, even in embedded spaces.\n\nThe entire mobile ecosystem has been nothing but an avoidable disaster of bad decisions from the start.\n\nThe realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. I2P is 20 years old. And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a /lot/ of countries.\n\nAnd right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general *completely* ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent Asynchronous Communication is a basic requirement and paradigm to build around, because infrastructure capable of lending itself to low-latency communication cannot be meaningfully assumed anywhere.\n\nSo yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.",
"mediaType": "text/plain"
},
"summary": "",
"tag": [
{
"href": "https://mstdn.social/users/kkarhan",
"name": "@kkarhan@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/PiTau",
"name": "@PiTau@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/rysiek",
"name": "@rysiek@mstdn.social",
"type": "Mention"
}
],
"to": [
"https://mstdn.social/users/kkarhan",
"https://udongein.xyz/users/lispi314/followers",
"https://mstdn.social/users/PiTau",
"https://mstdn.social/users/rysiek"
],
"type": "Note"
}
],
"totalItems": 5,
"type": "OrderedCollection"
},
"id": "https://udongein.xyz/objects/e380dee0-db9e-4aff-b6ff-a2730afc0315",
"inReplyTo": "https://mstdn.social/users/kkarhan/statuses/111378100236269307",
"published": "2023-11-09T03:47:51.433755Z",
"repliesCount": 3,
"source": {
"content": "@kkarhan@mstdn.social @PiTau@mstdn.social @rysiek@mstdn.social He does actually point out some alternatives from time to time, though maybe he does that more often on Fedi than on his site, I haven't really been paying attention that closely.\r\n\r\nAlso, we've yet to even just catch back up with what Lisp Machines were doing 20~30 years ago in terms of system design. There has been a *lot* of unix-brained regression that needs to be addressed before blaming any other party.\r\n\r\n(And Microsoft dropped [the last hope for common & good sense to prevail in their ecosystem](https://en.wikipedia.org/wiki/Singularity_(operating_system)) back in 2015 so that's the end of the line for them too.)\r\n\r\nWe're *still* writing new C code, despite knowing full well that's a terrible idea and having decades of easily-avoidable incident after incident to back that assertion. We've had perfectly viable alternatives for over two decades now, [even in embedded spaces](https://learn.adacore.com/courses/Ada_For_The_Embedded_C_Developer/index.html).\r\n\r\nThe entire mobile ecosystem has been nothing but an avoidable disaster made-up of bad decisions from the start.\r\n\r\nThe realization that the clearnet is fundamentally broken as anything but a routing layer isn't anything new either. [I2P](https://geti2p.net/en/) is [20 years old](https://geti2p.net/en/about/intro). And yet we still see new deployments on the clearnet and mass direct reliance on that transport layer despite knowing full-well its physical makeup has been purposely sabotaged to facilitate censorship and disruption whenever it's politically expedient in a **lot** of countries.\r\n\r\nAnd right, disruption tolerance, that's something the internet, TCP stack and low-latency networking in general *completely* ignores (yeah unfortunately I2P also loses on that one). Any reasonable assessment of the infrastructural difficulties that are routinely observed on a daily basis around the world should be enough to conclude that medium-diverse/independent/agnostic [Asynchronous Communication](https://www.complete.org/asynchronous-communication/) is a basic requirement and [paradigm to build around](https://www.complete.org/recovering-our-lost-free-will-online-tools-and-techniques-that-are-available-now/), because infrastructure capable of lending itself to low-latency communication [cannot be meaningfully assumed anywhere](https://www.complete.org/tools-for-communicating-offline-and-in-difficult-circumstances/).\r\n\r\n(By the way, neither [Fidonet](https://en.wikipedia.org/wiki/FidoNet) nor [Usenet](https://en.wikipedia.org/wiki/Usenet) made such [assumptions about infrastructure](https://mastodon.top/users/lispi314/statuses/111253066257920146). We've regressed a lot.)\r\n\r\nWe've also had ample time to observe that centralized infrastructures are basically optimized for easy takedowns, and yet the majority of current systems are still neither distributed nor P2P.\r\n\r\nSo yeah, I don't know, I don't think all of that can be blamed on the FSF when there's a lot of corposcum and malicious government intervention that directly contributed to this state of affairs.",
"mediaType": "text/markdown"
},
"summary": "",
"tag": [
{
"href": "https://mstdn.social/users/kkarhan",
"name": "@kkarhan@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/PiTau",
"name": "@PiTau@mstdn.social",
"type": "Mention"
},
{
"href": "https://mstdn.social/users/rysiek",
"name": "@rysiek@mstdn.social",
"type": "Mention"
}
],
"to": [
"https://mstdn.social/users/kkarhan",
"https://udongein.xyz/users/lispi314/followers",
"https://mstdn.social/users/PiTau",
"https://mstdn.social/users/rysiek"
],
"type": "Note",
"updated": "2023-11-09T04:27:50.656950Z"
}