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://join-lemmy.org/context.json",
"https://www.w3.org/ns/activitystreams"
],
"type": "Page",
"id": "https://lemmy.world/post/17671888",
"attributedTo": "https://lemmy.world/u/CAVOK",
"to": [
"https://lemmy.world/c/i2p",
"https://www.w3.org/ns/activitystreams#Public"
],
"name": "If you're one of the ~25 snap users, you can finally upgrade again!",
"cc": [],
"content": "<p>From the maintainer “alreadyburnt” on reddit.</p>\n<p>Before we begin: Snap(and AppImages) are still not official packages. This still an experimental package and just a side-project of mine.</p>\n<p>A few years ago, I got way too interested in these semi-novel packaging systems that the various distributions came out with. I went on a rampage of experimental package creation, often without necessarily knowing the future of the packages themselves. Many versions ago, the most popular of those packages broke in a particu`larly annoying way, and I did not have time to fix it. Until a few weeks ago, that is, and now, it’s actually a lot easier for me to be sure that what I’m packaging is going to actually work because I can generate and test the packages continuously.</p>\n<p>TL:DR the Snap, which I created, then broke, is now fixed, and it’s likely to stay that way. If you are a snap user stuck on an old version, update as soon as possible.</p>\n<p>It is generated using jpackage combined with the Easy-Install source. As a package, it functions like the Easy-Install bundle and not like the .deb or .jar installers.</p>\n<p><a href=\"https://snapcraft.io/i2pi2p\">snapcraft.io/i2pi2p</a></p>\n<p>What’s the real point? Nobody really cares about Snapcraft that much, except maybe Canonical. A lot of people don’t even like them. That’s not why there’s a Snap of I2P now. The reason there’s a Snap of I2P now, and that this experiment was not discontinued outright, is because it demonstrates the power of jpackage, the technology underlying the Easy-Install Bundles for Windows, to generate self-contained images that can easily be adapted to Linux package formats. Once you can stick a jpackage inside a Snap, you can just as easily stick it inside of an AppImage. A slightly different manifest format will leave you with a working Flatpak. The same applies to docker-compose and probably many other tools. Or, you can just stick it all into a .zip file and treat it like an I2P portable installation. The files your packaging are always the same, and are simply generated by jpackageing a custom I2P router launcher.</p>\n<p>For more information, see:</p>\n<p><a href=\"https://snapcraft.io/i2pi2p\">snapcraft.io/i2pi2p</a></p>\n<p><a href=\"https://github.com/eyedeekay/I2P-Snaps-and-Appimages/\">github.com/eyedeekay/I2P-Snaps-and-Appimages/</a></p>\n",
"mediaType": "text/html",
"source": {
"content": "From the maintainer \"alreadyburnt\" on reddit. \n\nBefore we begin: Snap(and AppImages) are still not official packages. This still an experimental package and just a side-project of mine.\n\nA few years ago, I got way too interested in these semi-novel packaging systems that the various distributions came out with. I went on a rampage of experimental package creation, often without necessarily knowing the future of the packages themselves. Many versions ago, the most popular of those packages broke in a particu`larly annoying way, and I did not have time to fix it. Until a few weeks ago, that is, and now, it's actually a lot easier for me to be sure that what I'm packaging is going to actually work because I can generate and test the packages continuously.\n\nTL:DR the Snap, which I created, then broke, is now fixed, and it's likely to stay that way. If you are a snap user stuck on an old version, update as soon as possible.\n\nIt is generated using jpackage combined with the Easy-Install source. As a package, it functions like the Easy-Install bundle and not like the .deb or .jar installers.\n\nhttps://snapcraft.io/i2pi2p\n\nWhat's the real point? Nobody really cares about Snapcraft that much, except maybe Canonical. A lot of people don't even like them. That's not why there's a Snap of I2P now. The reason there's a Snap of I2P now, and that this experiment was not discontinued outright, is because it demonstrates the power of jpackage, the technology underlying the Easy-Install Bundles for Windows, to generate self-contained images that can easily be adapted to Linux package formats. Once you can stick a jpackage inside a Snap, you can just as easily stick it inside of an AppImage. A slightly different manifest format will leave you with a working Flatpak. The same applies to docker-compose and probably many other tools. Or, you can just stick it all into a .zip file and treat it like an I2P portable installation. The files your packaging are always the same, and are simply generated by jpackageing a custom I2P router launcher.\n\nFor more information, see:\n\nhttps://snapcraft.io/i2pi2p\n\nhttps://github.com/eyedeekay/I2P-Snaps-and-Appimages/",
"mediaType": "text/markdown"
},
"attachment": [],
"sensitive": false,
"published": "2024-07-18T05:18:34.837735Z",
"language": {
"identifier": "en",
"name": "English"
},
"audience": "https://lemmy.world/c/i2p",
"tag": [
{
"href": "https://lemmy.world/post/17671888",
"name": "#i2p",
"type": "Hashtag"
}
]
}