I will just take this opportunity to highlight some updates to the API endpoints coming in the next version of PieFed (so far, we are actively working on more still):
Tons more user settings (I basically made it possible to control every single setting using either the web UI or the API)
Poll post support (including voting)
Event post support
Unsubscribe from everything endpoint (warning, this is irreversible)
Rating communities
Marking a comment as an answer (aka Stack Overflow)
In general, it has been a priority for us to make sure that when we add features these days, that we also make a corresponding API endpoint to do that same action. There is still plenty of things not in the API, but we are working our way through the backlog.
Lastly, I just want to send out a huge thanks to all the app/frontend developers that have very patiently been helping us debug all these things as we have been implementing them on the test instance. Also, a thanks to users like Sunshine that make sure to keep the pressure on us to make sure we don't forget anything!
lemmy-meter.info just checks the landing page and the API responses for a community, post and comment, and just logs them over time. These are all things, irrc, Piefed's API supports so I don't know why the API needs to be expanded to log server stability? What does Mlem do to show instance stability?
Thank you for the explanation. Though I haven’t learned enough Swift to be working on the app’s code myself, I mostly just do testing after reading the commits and issues.
@sjmarf@sh.itjust.works & @ericbandrews@lemmy.ml may be able to explain more in detail.
As you correctly observe below, we get uptime from lemmy-status.org, which doesn’t currently support Piefed. We do plan to expand this feature to Piefed, but it will require finding a new data provider and updating our code to process it, so our priority right now is adding support for features closer to the core interaction loop of the app.
I believe @mrkaplan@piefed.world is working on it. They just completed the upgrade to 1.2 within the past week and are working on the 1.3 upgrade process. They customize the code to some degree and run a FHF branch of PieFed, so it takes a bit of time for them to finish that process and test it.
11 Comments
wjs018@piefed.social · 22 pts · 256d
Same...
I will just take this opportunity to highlight some updates to the API endpoints coming in the next version of PieFed (so far, we are actively working on more still):
In general, it has been a priority for us to make sure that when we add features these days, that we also make a corresponding API endpoint to do that same action. There is still plenty of things not in the API, but we are working our way through the backlog.
Lastly, I just want to send out a huge thanks to all the app/frontend developers that have very patiently been helping us debug all these things as we have been implementing them on the test instance. Also, a thanks to users like Sunshine that make sure to keep the pressure on us to make sure we don't forget anything!
ekZepp@lemmy.world · 1 pts · 255d
FUCK YES!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
aarch0x40@piefed.social · 4 pts · 256d
You could always submit a pull request. Server stats should be easy to implement
flamingos@feddit.uk · 3 pts · 256d
lemmy-meter.info just checks the landing page and the API responses for a community, post and comment, and just logs them over time. These are all things, irrc, Piefed's API supports so I don't know why the API needs to be expanded to log server stability? What does Mlem do to show instance stability?
Sunshine@piefed.ca · 4 pts · 256d
Thank you for the explanation. Though I haven’t learned enough Swift to be working on the app’s code myself, I mostly just do testing after reading the commits and issues.
@sjmarf@sh.itjust.works & @ericbandrews@lemmy.ml may be able to explain more in detail.
The Mlem details tab shows this page:
flamingos@feddit.uk · 4 pts · 256d
I did some digging through the repo and found they query https://lemmy-status.org/ for this info.
Sunshine@piefed.ca · 1 pts · 256d
The Piefed instance settings are currently missing from the api.
ericbandrews@lemmy.ml · 2 pts · 256d
As you correctly observe below, we get uptime from lemmy-status.org, which doesn’t currently support Piefed. We do plan to expand this feature to Piefed, but it will require finding a new data provider and updating our code to process it, so our priority right now is adding support for features closer to the core interaction loop of the app.
finitebanjo@piefed.world · 3 pts · 256d
wjs018@piefed.social · 7 pts · 256d
I believe @mrkaplan@piefed.world is working on it. They just completed the upgrade to 1.2 within the past week and are working on the 1.3 upgrade process. They customize the code to some degree and run a FHF branch of PieFed, so it takes a bit of time for them to finish that process and test it.
finitebanjo@piefed.world · 1 pts · 256d
wjs018@piefed.social · 2 pts · 256d
For removing the bottom bar, use the css from this post in your user custom css: https://piefed.social/post/1278887
Blaze@piefed.zip · 1 pts · 256d
You can always create an alt on Piefed.zip
ekZepp@lemmy.world · 1 pts · 255d