Hacker News new | past | comments | ask | show | jobs | submit | ahdinosaur's comments login

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


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! ️️


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. =^.^=


What that invite will do? Will it let me join a public network or a private? What does it mean? Is it like an IRC channel or a reddit subreddit (pub/pvt)? Or it will let me just connect to you and some degree of your connections (like a network of people knowing each other -- kind of a pub/pvt club)?

I am sorry to ask these (I guess mundane) questions here but I tried the docs and it isn't really clear. Also patchwork desktop app brought my laptop to a standstill so couldn't explore much.


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.


Great. Thank you!

Can I choose to sync just the new content since I joined? Or since let's say June 2017? And can I clear the previous content synced on my device? If nothing then, let's say, for need for free disk space.

Also, I have installed the Manyverse app on my Android phone (hoping it would not be as resource intensive as Patchwork) - but shall I have do everything all over again if I ever to go for a desktop app or any other app on any device (as it seems from other comments in this post) - every invite being added again and so on?

(Edit) And Manyverse is another decentralised app that is using ScuttleButt protocol, right? And the Android app is a way to access "just this app/social network" on the SSB network - or not on a network really since it's P2P. Did I get it right?

I have watched the video and it made things a lot clearer and the heartbreaking story was touching :) But now I think Manyverse might just be a "pub" on SSB :)


> 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 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.


I looked at the faq, but it's rather non-technical. Is there a security/privacy faq? My initial reading is that it's a lot like Twitter or things shouted out in a pub that films and archives everything that goes on? : no expectation of privacy, no secure private messages, no deniabilty?

Ed: looks like https://github.com/ssbc/scuttlebot/blob/master/README.md has a bit more meat. Still happy to hear any comments. Especially I assume any recipient can prove to a third party that someone said something?


The real meat of the protocol is explained here:

https://ssbc.github.io/scuttlebutt-protocol-guide/

> I assume any recipient can prove to a third party that someone said something

All public messages are signed with the author's key, so any third-party can verify it.

Private messages are different, though. You need one of the recipient / sender's keys to decrypt that, and so for a third-party to verify it they would need one of those private keys.


This was true until about 14 hours ago. :)

https://github.com/ssbc/secure-scuttlebutt/pull/220

You can now generate an unbox key for a private message send it to a non-recipient for them to be able to access the message, which is really cool. No private key sharing necessary!


That is cool. But the point stands that public (to all) and private (to designated recipients) messages are "on the record" and can forever be proven to be made by someone that held your private key at the time?

So if I say: "let's fight racism!" and you later decide to collaborate with a (now) racist government - you could prove (not merely allege) that I should go to the gulag?


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. :)


I too find it a bit discouraging that my data would leak away to the whole network eventually. I'd like to have "an island" (I believe this metaphor was used in some docs) to myself and those close to me. Or maybe I haven't yet grasped how SSB works.


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.


How does discovery happen in Cabal or in Scuttlebutt?

Does it use any kind of DHT like Kademlia? I know you want to avoid singletons but are there any hubs that are DHTs or what? How does discovery work? And do you support Web Push?


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


To be fair to real life there's a reasonable chance of forgetting :)


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! mikey@rootsystems.nz

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.


i am interested to know about usage characteristics for running a Pub (bandwidth, storage, CPU) to be able to gauge what it will cost me to host one myself.

curious to know about your experience with that.

also is there a way to set rate limits?


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....


Oh sorry! I didn't realise.

Scuttlebutt is definitely in need of a consolidation of information. Keep up the good work!


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.


Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: