NireBryce

reality is the battlefield

the first line goes in Cohost embeds

🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮

I speak to the universe and it speaks back, in it's own way.

mastodon

email: contact at breadthcharge dot net

I live on the northeast coast of the US.

'non-functional programmer'. 'far left'.

conceptual midwife.

https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut

If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.


atomicthumbs
@atomicthumbs

still sad that posts and people are as yet Undiscoverable if you don't follow them or share them or something. or if you're lucky enough to stumble into a tag they used. the site is still small enough that a public view of The Cospace wouldn't be overwhelming, but who knows how long that will remain the case


NireBryce
@NireBryce

I would love a search function so I can find, say, the 3d eggbug once people stop retweeting it, six months later when I remember it again when very high


atomicthumbs
@atomicthumbs

God imagine if there was just a fuckin slider on top of the timeline labeled NETWORK LINKS. default setting is 1 and it shows posts by people you follow. you can crank it up to 2 to also see posts by people they follow. all the way to "6+" where it shows the entirety of cohost


NireBryce
@NireBryce

a slider from 'cozy' to 'fuck me up' and none of the detents are labled


nex3
@nex3

I've been pondering since early on in Cohistory how to expose new comments on posts you've already seen, and I think a solution for that could dovetail with this. Imagine scrolling through your feed and reaching the newest post you already saw. At this point, your most fervent desire is more fresh chost. You see a little interstitial with two links: "3 new comments on old posts" and "show network posts". Each of these takes you to an ancillary timeline, one that shows comments and one that shows posts from people followed by people you follow.



You must log in to comment.

in reply to @NireBryce's post: