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):
- 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)
- The mark as AI label
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!
FUCK YES!!!
You could always submit a pull request. Server stats should be easy to implement
deleted by creator
I would also really like to request piefed.world update their /*/*ing version plz
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.
@mrkaplan@piefed.world do we know when images in comments will begin to work? Also, small nitpick, can we add a setting to remove the menu bar at the bottom while in mobile? I keep accidentally redirecting while typing comments.
Also hows funding been?
For removing the bottom bar, use the css from this post in your user custom css: https://piefed.social/post/1278887
You can always create an alt on Piefed.zip
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?
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.
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:
I did some digging through the repo and found they query https://lemmy-status.org/ for this info.
The Piefed instance settings are currently missing from the api.
