ahdinosaur

Hi, I made an archive of videos that changed either computer history, how I see computation, or how I see the world.

Hosted on my PeerTube server. Hope you enjoy, open to suggestions for other videos, thanks.

local to me is Flick Electric in New Zealand: https://www.flickelectric.co.nz/freestyle

> Can I choose to sync just...

at the moment no, but it's likely we'll move content off-chain (%QJEpN8LN1t3BrIkUQ3WoOMWRsMArbVUZCpTeBYcuqfw=.sha256) so you would only need to sync the signature chain metadata, then could choose what content you want to download or delete.

> But now I think Manyverse might just be a "pub" on SSB

Manyverse is a mobile app on SSB, much like Patchwork is a desktop app. it uses all the same peer-to-peer network, including the existing pubs (as in there are no pubs specific to Manyverse).

> shall I have do everything all over again if I ever to go for a desktop app or any other app on any device

if you want to use both Manyverse and Patchwork, yes they will be separate keys each with their own feed, to be merged as the same conceptual identity, see this comment: https://news.ycombinator.com/item?id=18067100.

hi dmos62, Scuttlebutt is designed to allow users to create social communities with trust-based boundaries, but there's just a lot of work to do to bring our implementation up to match our intentions. for example here's a recent step in that direction: https://github.com/ssbc/ssb-incoming-guard.

hi balladeer, the invite is created by my pub (a peer that has a public ip address and is always online), when you use the invite:

- the pub will post a message to follow you - you will post a message to follow the pub - you will post a message advertising the pub on your feed

basically this mean you will become connected to the pub's social graph (by following the pub) and vise versa the pub will replicate your messages (by the pub following you).

also to note, in the future we will change the pub invite story: invites are directed from one user to another user and pubs are only a messenger (%LMYARKcJ5/HVrkfyGo0oSV4j/whFmpeiJlQnvPw53PE=.sha256), and pubs will become just another device controlled by a specific user (%Gwqklkj0b2CBT5tPiz5170NWsPp3xiuLbOImEaG/e+4=.sha256)

happy to answer any questions! also, i know the initial sync is pretty intense at the moment (joining most public pubs means joining an active community with years of content!), but once it's done it's done, later you only sync what you missed since you last sync'd.

this invite will no longer work, but unfortunately i can't delete the post. find me at dinosaur.is, send me an email or a twitter dm if you want an invite. =^.^=

hi e12e,

yes, on-chain messages are designed to be "on the record" (https://viewer.scuttlebot.io/%25G7BjZsZr02TPAoIeD%2Bw3WgiAbi...), where the game theory is of an infinitely-repeated game (https://en.wikipedia.org/wiki/Repeated_game#Infinitely_repea...) where participants have verifiable knowledge of past game activity, which is useful for trust-based coordination.

our plan is to eventually add a side protocol for off-chain ("off the record") messages which re-use the same cryptographic identities, for all your other conversations. :)

hi, if anyone wants to start with a public social network (instead of building one with your existing friends), here's an invite:

many.butt.nz:8008:@o3OcykTU7zdsm+WKoGl74XAoyDI/SWlVbIeyHHinQXQ=.ed25519~Se1dEm/vb/9c/pKs9eqGY7514p0b7KdR5/+myMIKCKo=

welcome to the 'verse! ️️

hi Jahak, the server code for each peer in the social network is here: https://github.com/ssbc/scuttlebot/

hi gregknicholson, i'll try! =^.^=

Scuttlebutt is a social network platform where each uxer has a personal diary where each page is a signed message that links to the previous page. to receive updates on someone's diary, you follow the person. on each page, content is free-form. the most common message type is 'post', but there's a chat app (similar to Cabal) that uses message type 'scat_message': https://www.scuttlebutt.nz/applications#scat.

Cabal is a chat app, built using the Dat protocol (https://datproject.org/). Dat has a similar architecture, except the diaries (sigchains) are centered on content rather than people. so to receive updates on a diary, you follow the _content_, which in Cabal is a chat group similar to a Slack group.

hi fareesh, as with real-life, you can't take back what you said, you can only apologize (in a new post). :)

there's talk of moving message content out of the sigchain so you could "delete" (ask your peers to delete) a post: %QJEpN8LN1t3BrIkUQ3WoOMWRsMArbVUZCpTeBYcuqfw=.sha256

hey, have you tried contacting a private pub? i'm Mikey, owner of `one.butt.nz`, happy to give you an invite if you send me an email! [email protected]

if you want to setup your own pub, i made an automated Digital Ocean installer (also a detailed manual) for a Docker-based pub: http://github.com/ahdinosaur/ssb-pub.

i'm also working (with funding from #ssbc-grants) on a hosted pub-as-a-service product: http://buttcloud.org.

hey @brad0, as far as i know, ssbc.github.io is the most out-of-date, at the time of being written by @pfraze it was superseded by scuttlebot.io which has all the same detail and more.

scuttlebutt.nz is a more recent effort by me to write documentation not only about the technical details of _how_ but also more stories and quotes to capture the spirit of _why_.

but having documentation scattered around is confusing, our intention is to consolidate these many sources into scuttlebutt.nz: https://www.scuttlebutt.nz/contributing.html#contributing-do....

hey @atestu, i agree it's confusing.

this page on scuttlebutt.nz should help: https://www.scuttlebutt.nz/modules.html#secure-scuttlebutt-v...

feel free to ask if you have more questions. :3

what happens "in real life" when two people go by the same name?

Scuttlebutt works the same way: anyone can name themselves anything and anyone can name other people anything, it's up to the client how to interpret those messages. more on how SSB embraces subjectivity: https://youtu.be/P5K18XssVBg.

the [LEBRON stack](http://lebron.technology/) using many small npm modules is my favorite, but i add Backbone and React when i'm working with others who want something more framework-y.

also DocPad for static sites with more content than code.

i'd suggest https://github.com/primus/primus. it's an abstraction layer for real-time so no lock-in to a single socket implementation. it's simple and extensible by plugins.

Debian for personal computers and servers. OpenWRT for embedded devices.

I work around this problem in a couple projects by putting my code in modular directories in ./src/node_modules. no npm magic, no having to make symlinks or change path, just plain node. it also makes it very easy to publish your modules when you are ready, just take the module directory out, give it a package.json, npm publish the module, npm install --save the module back in the project.