Email or username:

Password:

Forgot your password?
Top-level
Alex Gleason

@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.

11 comments
a1ba-nyan
@alex what you're trying to do is really hard and what you can export to the API highly depends on the exact implementation and tradeoffs you're gonna make.

Especially in fedi software. For example: editing. Yes, I'm whining about post editing all the time but on other hand, it was a tradeoff for federation and I understand it. Therefore there is no dedicated API export and moreover, API helps client devs to implement an alternative. Very bad on technical side but it works for users.
@alex what you're trying to do is really hard and what you can export to the API highly depends on the exact implementation and tradeoffs you're gonna make.

Especially in fedi software. For example: editing. Yes, I'm whining about post editing all the time but on other hand, it was a tradeoff for federation and I understand it. Therefore there is no dedicated API export and moreover, API helps client...
Alex Gleason

@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.

a1ba-nyan
@alex then, well, good luck.

I still recommend you to read AP proposals written by @grishka , he also makes some kind of groups, in more VK-like style than Reddit-like
Gregory

@a1batross @alex@gleasonator.com а что в оригинальном посте было?

a1ba-nyan
@grishka alex тоже грозится сделать группы, правда начал с хвоста -- клиентского API.

Ну я ему и сказал, что то что он хочет уже делаешь ты. Он в курсе и оглядывается на твой проект. :)

Полный тред: https://gleasonator.com/notice/A8QVsVHwkVHhP1lTBg
Gregory

@a1batross лол, клиентское API. Это то, что я буду делать в последнюю очередь.

a1ba-nyan
@grishka о чём я и сказал. Как слепишь, таким и интерфейс будет, а не наоборот
Gregory replied to a1ba-nyan

@a1batross ну на самом деле так тоже неправильно. Сначала ты придумываешь UX, а потом — всё остальное, чтобы его реализовать. Иначе получится десктопный линукс.

Alex Gleason replied to a1ba-nyan

@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.

a1ba-nyan replied to Alex
@alex I've seen projects where people started from building from frontend, users get interested but nothing happens due to different reasons.

That's why I got disappointed with Pixelfed for example. While it looked nice on frontend, it federated poorly which made first impression worse. Maybe I should try it again.

That's just my personal subjective observations with different projects, open source or not. So no offense please.

also retranslating parent post for @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.
@alex I've seen projects where people started from building from frontend, users get interested but nothing happens due to different reasons.

That's why I got disappointed with Pixelfed for example. While it looked nice on frontend, it federated poorly which made first impression worse. Maybe I should try it again.
Gregory replied to a1ba-nyan

@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.

Go Up