Stories

Comment by bc3mc2

Comment

Comment by bc3mc2

Hi all, I've been working on a p2p media app that uses webtorrent basically in round table bubbles. Its basically a Venn Diagram I figure you need peers for p2p and for social sites so why not put the two together. Yes its another group chat and yes its social media but its also webtorrent. It uses graphql which makes for some interesting data structures, and it has a livestream from webtorrent. Its quasi-live as in there is a delay and it posts in 8 second chunks that are assembled on the client side. Its called bubbleBASED because its bubbly & based.

I have about hopefully a week left until it is where I want it to be, any feedback I'll put into the app. The global UI isn't amazing right now but if you login its better but I figure having the public stuff is good for seo and discovery.

It has a cdn under it all but its creative with trying to use as much webtorrent as is reasonable/unreasonable. The app has been closed behind privacy walls for a while and I'be been building the public layers in this week.

The intent is to have social media that doesn't try to cram as much stuff in front of your eyes as is chosen by the algorithm. Like when you boot up this app you get your own home bubble and you can see public "bublic" and global bubbles. Global bubbles are what you see here, they exist outside the app. Private bubbles you will never see unless you are in one, and the 'bublic' bubbles are in app only. The stream follows suit in terms of you stream to a bubble and if you are in the bubble you see the stream.

I have some work to do with routing the livestreams (right now they all coalesce in one tab but I want them separated so you can share just one livestream and not see the entire bubble. Stuff like that but its graphql and its annoying lol.

Basically the key to this thing is that it shares the metadata quickly to users so they know where the magnetlinks are, and I run a tracker to connect seeders/feeders. There is no aws or s3 buckets or anything like that but there is mongodb and heroku and ipfs & piñata (cdn and pinning) and a lot of caching (and i have some backend caches i still need to reconnect). Also it uses the idbchunkstore its a webtorrent thing that stores torrent data in indexeddb to keep swarms going. I figure lets be the data center why not.

Its also an attempt to have a human algorithm (oh the humanity). And there is an option to submit a cj.com affiliate link if you want to add one to your profile the site picks at random and places them so its a community monetization thing. Its also an attempt to reconnect people to their actual social media communities so people aren't shadowbanned/throttled/promoted/excluded. There are more privacy controls on the way (bubble visibility etc). User can select public or private right now so even if they post in a global (web facing) bubble the site doesn't print those so no one will see. I want member lists to be the same way, stuff like that but you have to deal with the db a lot :). Private bubbles are invite only at the moment so you actively have to get people to your bubble (or join from an invite).

Anyways have a great week and thanks for checking it out.

Replies bc3mc2 · 15d
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    New collection

    Delete this collection?

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Privacy policy · Terms of use

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.