Curious about Lemmy and boy, we're not making this easy are we?
1. Lemmy or kbin?
What is the difference? Do they still aggregate the same things? Just getting my head wrapped around the difference is confusing.
2. Lemmy requires me to join a server?
Not this again... I DON'T care what the server's 'topic' is. I just want something that is reliable so I can see MANY topics.
Note: I really REALLY don't want you to help me (I know the answers)
I'm pointing out a #UX problem
@scottjenson The worst part of most current #Fediverse implementations:
They bundle the reader part and the publishing part.
It’s like bundling Google Reader within WordPress.
Totally needless. (And something I think the #IndieWeb is getting more right with eg #MicroPub, ensuring reading, aggregation, publishing etc doesn’t have to all be in a single application / server)
@scottjenson I want one single central profile for myself that aggregates my activity from all across the web, a livestream basically.
Like what @chrismessina mocked up here: https://www.flickr.com/photos/factoryjoe/3122318414/
There’s plenty of room for differing opinions in this, but I think this was the big thing that social media got right. Responding to others from right inside your reader… that was the killer change that made RSS go away. @voxpelli @scottjenson
@benpate @scottjenson Oh, but there is no need to _host_ your reply within your reader, you simply have to be able to _write_ your response within your reader.
Eg: I use @ivory as a client for my Mastodon account and it both reads and writes to that Mastodon account (using the Mastodon-specific API?)
With #indieweb it instead could do:
- Read the content using a standard protocol like #MicroSub: https://indieweb.org/Microsub
- Write any actions / replies using #MicroPub: https://indieweb.org/Micropub
For sure. It would be nice to have the option to mix and match services. Open APIs help keep vendors honest. But most people need a plug and play solution that works without a lot of extra thought. Complex machines won’t be the solution for most. @voxpelli @scottjenson @ivory
@voxpelli @scottjenson to be fair, wordpress does that too at https://wordpress.com/read
@KevinMarks @scottjenson Was thinking the open source version
@scottjenson however, I know nothing and would like to be enlightened. I haven't figured this mess out yet
@scottjenson Lemmy existing at the same time as kbin doesn’t sound like a UX problem to me.
Could you expand on your last point? When I look at the structure of the Fediverse, I don’t see an answer to the “choose your server” UX problems. If you see a way out of this mess, pleeeeaaase shine a light in the right direction?
@benpate I've talked about this quite a bit. There are a few points I'll try to cram in:
1. There is nothing wrong with servers, they are just hard to explain
2. The choosing mechanism is broken, focusing on topic, which is fairly meaningless. Showing Covenant 2.0 adopters which would offer much more confidence. Same with funding/bylaws.
3. Many people don't care, just have a short list of well run servers and default to one (with the option to pick) Things are improving here.
@scottjenson@social.coop Now that I've switched to #Calckey, I've been dealing with a fair amount of downtime. Hey, groovy. New shit, it breaks. I get it.
But that means I've missed conversations about "Covenant 2.0". I found this via searching: https://github.com/bildpunkt/fediverse-friendly-moderation-covenant/blob/master/covenant.md
Is that the spot? Or is there another resource you can point me to? We're about to spin up a #kbin instance and open it up, and I'd love some guidelines to follow. (Though I do love whipping out the #banhammer when warranted!)
@Evoterra @scottjenson@social.coop also, there's other Calckey instances that may abide by a covenant: https://calckey.org/join
But the covenant is for permanent shutdowns, not maintenance.
@kainoa @scottjenson @Evoterra Is there a list of servers that have pledged to abide by that covenant?
@gme@bofh.social @scottjenson@social.coop @Evoterra@calckey.social probably not, because that covenant is very mastodon-oriented. All of the servers on the calckey list abide by our server guidelines: https://codeberg.org/calckey/calckey.org/src/branch/main/SERVER_GUIDELINES.md
@Evoterra @samhenrigold might be the right person to talk to about Conveant 2.0. Last time we talked it was "on the radar" but I would certainly hope it's getting closer, it is sorely needed (and of course used)