Chronotope’s Twitter Archive—№ 106,759

I have been fiddling with the idea of 1-shot conference social networks & like most of my side projects I've bitten off more than I can chew, but it has me thinking a lot about how we think of the role of Commenter one-dimensionally.
On twitter.com ♻️ 1 Retweets ❤️ 8 Favorites 2019 Jul 8 Mood +2 🙂

…in reply to @Chronotope
I was exploring options with setting up commenting via coralproject and reading their code and docs so lots of credit to them on being thoughtful about this stuff. Mostly I was thinking about how both privacy tends to be binary and commenter tends to be an un-expandable role...
Permalink On twitter.com ❤️ 4 Favorites 2019 Jul 8 Mood +2 🙂

…in reply to @Chronotope
Inspired by SRCCON's photo policy, I'm wondering if it can't expand further on both of those things. What if commenters had four levers of control: access, amplification, revocation, and retention.
Permalink On twitter.com ❤️ 3 Favorites 2019 Jul 8 Mood +1 🙂

…in reply to @Chronotope
- Users can control what types of users get access to their posts. - Who can amplify their posts and in what contexts, along with what responses get amplified - What posts have revokable access - What posts can be retained by another person or system w/ or w/o the users' ID
Permalink On twitter.com ❤️ 7 Favorites 2019 Jul 8 Mood -1 🙁

…in reply to @Chronotope
I've been reading a lot about commenting systems and about federated systems and I've just been thinking a lot about how we have very different tools for commenting, communicating and moderation than we had even a few years ago.
Permalink On twitter.com ❤️ 3 Favorites 2019 Jul 8 Mood 0

…in reply to @Chronotope
Been playing with a prototype of how this would work but it isn't even close to functional. Dunno. What do people think of a model that builds on those types of controls? Might write it out in more detail so someone smarter than me could help think it through.
Permalink On twitter.com ❤️ 1 Favorite 2019 Jul 8 Mood +4 🙂

…in reply to @Chronotope
I think in code terms I may have to dumb down my project from my initial attempt, in order to get an MVP even working, maybe just build out my own very basic systems and leave the more complex tools I'd like to extend until later.
Permalink On twitter.com ❤️ 2 Favorites 2019 Jul 8 Mood -1 🙁

…in reply to @Chronotope
It really sucks that Node-based development forces you to do a whole lot of tooling work at the very beginning when you want to be just getting code and prototypes together. Perhaps I need to explore different side project methodologies as well.
Permalink On twitter.com ❤️ 4 Favorites 2019 Jul 8 Mood -2 🙁

…in reply to @Chronotope
Anyway, if you're interested in a more cohesive essay format of this idea, speak up and I may write it out for the next newsletter or something like that.
Permalink On twitter.com ❤️ 3 Favorites 2019 Jul 8 Mood +4 🙂

Search tweets' text