But when you will make on AP side(if you will), will you make it co-operable with other software like Lemmy or Smithereen? Lemmy already has working groups (sorta) and Smithereen dev working on AP proposals.
Top-level
13 comments
@a1batross API namespacing is explained in the first paragraph. “Anyone can do it”, except they didn’t. It’s a first step, to define the user functionality, and now I’m working on server-to-server. Don’t just say “I’m gonna be pessimistic” and then continue saying it. If you have to start with that, maybe it’s a sign you should rephrase what you’re gonna say. @a1batross I agree with that. But I also think I can do it. This is literally the only thing I’m going to work on for 3 months straight, all day long. I have the time. @grishka alex тоже грозится сделать группы, правда начал с хвоста -- клиентского API.
Ну я ему и сказал, что то что он хочет уже делаешь ты. Он в курсе и оглядывается на твой проект. :) Полный тред: https://gleasonator.com/notice/A8QVsVHwkVHhP1lTBg @a1batross ну на самом деле так тоже неправильно. Сначала ты придумываешь UX, а потом — всё остальное, чтобы его реализовать. Иначе получится десктопный линукс. @a1batross @grishka I started with the client API first because I am building for users first. If I have to adjust it, I will. I hope I can communicate with grishka some way. Maybe we can work together. @a1batross @alex@gleasonator.com oh, yes, Pixelfed. It does look nice, but last time I tried it, federation felt very much like an afterthought. The UI is built as if every instance is the only one. When you want to like or comment something, it just throws a login form at you. |
Yes Pleroma needs an API fork but it's better to avoid future incompatibilities.