Conversation:
Notices
-
@takeshitakenji @archaeme @loki Or rather, we'd have to if I gave a fuck. I've made a point of not wasting my time fixing Mastodon's problem.
-
@takeshitakenji @archaeme @loki 99% of the problems Mastodon has are stuff we have directly explained to Eugen how to deal with and fix. He just doesn't care and thinks he knows better. I stopped wasting my breath.
-
@archaeme @takeshitakenji @loki This is exactly why I've told people I'm not changing anything in the existing API. It breaks backwards compatability.
I'll make a new one others can use instead, sure, happily, but I'm not going to break the old API.
-
@loki @takeshitakenji @archaeme The existing API gives you a bunch of information you don't need on every API call. So you end up hammering the database for even just simple things. Not to mention it doesn't distinguish between notices and notice-like activity verbs like reposts, follows, and favourites (which is why favourites appear as notices in Mustard for instance).
-
@takeshitakenji @archaeme @dogjaw @loki Guy gets paid over 500$ a month to develop that piece of software, he doesn't need old May to hold his hand.
-
@loki @takeshitakenji @archaeme Sure, the client can and often does make the differentation based on the content of the notice, but why should it have to?
-
@loki @takeshitakenji @archaeme The qvitter API code does a lot to try to fill in the MANY holes the vanilla API has. There are many.
-
@loki @takeshitakenji @archaeme Yes, though I've been meaning to look into how difficult it would be to move that code into the core software.
-
@takeshitakenji @archaeme @loki It's one of the many, many things on my todo list for postActiv, there are a few.
-
@loki @takeshitakenji @archaeme https://www.postactiv.com/docs/
You're welcome.
(I got a lot of code to get through though, and I need to update the default naturaldocs template to be less late 90s/early 2000s)