Live data from Hacker News

Unwalled.Garden: souped-up RSS for P2P social apps

pfrazee.hashbase.io

41–50 of 54 posts

Re: Unwalled.Garden: souped-up RSS for P2P social apps

#41

At first glance -- and that's an important caveat, since I haven't dug in -- this looks like it's duplicating an awful lot of work that's already been done in the IndieWeb using existing, well-established protocols. https://indieweb.org

this is for the DAT protocol, not the legacy web (atm)

Re: Unwalled.Garden: souped-up RSS for P2P social apps

#43

Is there a reason to keep the post type out of the JSON and store it as file metadata? That works in Dat which supports file metadata, but what about when the data is handled in other ways (as plain files on disk, etc)? https://unwalled.garden/docs/how-does-it-work

It's not in metadata, it's in the directory structure!

Re: Unwalled.Garden: souped-up RSS for P2P social apps

#44
post #40
post #21

Earlier quoted context omitted.

Yeah I knew there had been some shots at it, but my google fu couldn't pull up anything solid to point to. I'd love to see if somebody ever tried to "go big" with RSS. EDIT: also the comments RSS is generally comments posted to the blog, right? Not quite the same thing as each user having their own RSS feed with their posts and comments.

The thing is, RSS is about dissemination of content while follow/like/comment is more about dissemination of opinion. There were indeed some protocols to fill the missing pieces, including json-ld for having some sane, common format and the Salmon protocol to make information go back up to the source. Like a salmon. But it definitely was a patchwork of multiple technologies with various advancement status and quasi-i…

Webmentions is a more modern protocol for this sort of functionality.

Re: Unwalled.Garden: souped-up RSS for P2P social apps

#45
post #27
post #25

Earlier quoted context omitted.

I don't follow you. JSON is very extensible. Just add a new key like "body-image" and you're done. How is that different from XML if your body is defined as a text field?

How do you express "Why didn't you use XML!?" with json?

Assuming It's eventually going to be read as HTML I do this

  {"body":{
    "childNodes": [
      {"span":{"textContent":"Why didn't you use "}},
      {"img":{"src":"xml_has_its_uses.png"}},
      {"span":{"textContent":" XML!?"}}
    ]
  }}

Re: Unwalled.Garden: souped-up RSS for P2P social apps

#46
This all sounds pretty exciting. I’ve been using dat/beaker and I love how easy it is to make a site right in the browser. It made me realize how many barriers there are on http to just build a personal website and host it for free.

This update to beaker makes sense to me as it was pretty hard to discover new sites on the network though I’d love to see dat become a bit more stable. I’d often make a site and a friend wouldn’t be able to connect to it. I think if these issues could be resolved is some way the whole network would really take off.

Re: Unwalled.Garden: souped-up RSS for P2P social apps

#49
post #47

What is the likelihood of Beaker running on Android?

Looks like the Bunsen Browser. It is fun to play with although I've never seen so many JavaScript errors without running developer tools. I was unable to load Unwalled Garden which sounds expected given that you are still building a new version of Beaker to support UG features, right?

Re: Unwalled.Garden: souped-up RSS for P2P social apps

#50
post #26

>Unlike Twitter and the other social networks, RSS never tried to capture the social graph, likes, comments, annotations, retweets, and etc of its userbase. It limited itself to posted content (mostly blog posts) and that was a missed opportunity. >missed opportunity Maybe it's just me, but RSS being all about content is the best thing about it.

This is the two competing goals of every publishing mechanism - one person wants to broadcast their data and another wants to consume it, and it's very rare for both parties to want exactly the same thing.
Post reply on HN