wjs018

joined 2 weeks ago
sorted by: new top controversial old
What are your ideas to improve PieFed? Vote for your favorites! in c/piefed_meta@piefed.social
[–] wjs018@piefed.wjs018.xyz 6 points 19 hours ago (1 children)

Add ability to use keyword filter on community names

This should already be live. In your user settings on the Blocks & Filters page, you will want to look for these options:

Since you are on piefed.social, rimu has tried to designate basically all the meme communities as "low quality" so that they are easily filterable by checking that box (new ones pop up all the time though). Additionally, the text box below lets you filter based on community name.

What are your ideas to improve PieFed? Vote for your favorites! in c/piefed_meta@piefed.social
[–] wjs018@piefed.wjs018.xyz 5 points 19 hours ago (1 children)

I'd like to sort communities by Top X amount of time, IIRC that was already in the works.

This is already live. If you are viewing a community, click Top in the bar and it should be a dropdown menu where you select the timerange:

If you are on a small mobile screen (like using the PWA), the different time options are listed out with the other sort options:

What are your ideas to improve PieFed? Vote for your favorites! in c/piefed_meta@piefed.social
[–] wjs018@piefed.wjs018.xyz 2 points 21 hours ago

Yeah, that should work then. I haven't really looked at that portion of the code, but I can try to take a peek.

What are your ideas to improve PieFed? Vote for your favorites! in c/piefed_meta@piefed.social
[–] wjs018@piefed.wjs018.xyz 7 points 22 hours ago (2 children)

Hmm, that is an interesting idea...

I might look into this one. Would something like voting buttons in the crosspost dropdown be an acceptable alternative? I think I would prefer to keep 1 action (click) means 1 vote, but making it easier to vote on crossposts makes sense with the way that piefed consolidates comments.

So, voting buttons here maybe? (no promises, just an idea) -

What are your ideas to improve PieFed? Vote for your favorites! in c/piefed_meta@piefed.social
[–] wjs018@piefed.wjs018.xyz 6 points 22 hours ago

This is planned for the 1.2 release (at least it is on the kanban board).

What are your ideas to improve PieFed? Vote for your favorites! in c/piefed_meta@piefed.social
[–] wjs018@piefed.wjs018.xyz 3 points 22 hours ago (3 children)

Do you mean on the bar with the voting buttons instead of being behind the three dots menu?

What are your ideas to improve PieFed? Vote for your favorites! in c/piefed_meta@piefed.social
[–] wjs018@piefed.wjs018.xyz 4 points 23 hours ago (2 children)

Are you using an app or the web ui? It is still an open issue that posts are not being marked as read when they are interacted with via the api. It should work as expected if you use the web ui.

What are your ideas to improve PieFed? Vote for your favorites! in c/piefed_meta@piefed.social
[–] wjs018@piefed.wjs018.xyz 7 points 1 day ago (1 children)

I've done a lot of work on the markdown to html edge cases. So, I think things like bold and italics intermingling and garbling each other shouldn't happen any more. If it does, feel free to let me know!

What are your ideas to improve PieFed? Vote for your favorites! in c/piefed_meta@piefed.social
[–] wjs018@piefed.wjs018.xyz 4 points 1 day ago (1 children)

I don't think that's the issue since you can upload images for an image post. It's more the effort of doing file uploads from a dynamically inserted part of the page (the reply box). I don't know enough Javascript to be able to do that.

Mobile Browser - Leave button placement in c/piefed_meta@piefed.social
[–] wjs018@piefed.wjs018.xyz 8 points 1 day ago (2 children)

Not a bad suggestion. When you are browsing the /communities page for example, the leave buttons are in the warning color (yellow if you are using the default dark theme) while the join buttons are in the primary color (blue). I can try to whip up some code for this.

7
Site and Misc Endpoint Updates (piefed.wjs018.xyz)
 

As part of our ongoing effort to make the piefed api self-documenting and validate the input and output, there have been a couple tweaks to the api. I realized that I should probably document them here since not everybody is keeping tabs on every codeberg PR that comes through the repo.

  • canAuthUserModerate has been renamed to can_auth_user_moderate in the CommentView schema. This transitioning from camelCase to snake_case will be a theme as I work my way through the endpoints, this is just the first that I ran across.
  • The title field in the PersonView schema will now be equal to the user_name instead of null if the user never set a display name. The way this was handled was a bit inconsistent between local and remote users, but now all users should have this behave the same way.
  • All of the timestamps in the InstanceWithoutFederationState schema have been standardized to the same format. Previously, these were in the standard iso format, but didn't have the Z at the end.
  • The Site schema can now return the site sidebar in html and markdown (if both formats are present). The sidebar field will continue to be html, while the new sidebar_md field will provide the markdown rendition of the sidebar. In the past, the sidebar was only in html, so the markdown version will only become available after an admin updates their instance's sidebar to use markdown instead of html.

That's all the changes that are live up to this point. I will continue to make posts in this community as changes are made to try to keep you all in the loop.

While we are talking about the future, other plans for the future are to have a dedicated development instance for testing bleeding edge code while keeping piefed.social on a more stable branch. In the meantime, feel free to peruse my instance's swagger ui (json version), which is up to date with the api changes as I am working on them (community endpoints are next).

400 Errors when hitting API endpoint `alpha/site` in c/piefed_api@piefed.social
[–] wjs018@piefed.wjs018.xyz 2 points 1 week ago

I think that is fine and don't see a problem with that. As for when this issue will get fixed, I merged a fix so other instances hopefully don't get it, but that won't make it onto piefed.social until the Kiwis wake up and @rimu@piefed.social is back online.

400 Errors when hitting API endpoint `alpha/site` in c/piefed_api@piefed.social
[–] wjs018@piefed.wjs018.xyz 3 points 1 week ago* (last edited 1 week ago) (1 children)

Ok, I was able to reproduce this and made a PR for a fix. This issue only pops up when a user has instance blocks and works fine otherwise, which is why others in this thread (and myself when I was testing) aren't running into issues.

The root cause really is that I was creating schema for input and output validation to match the manually created swagger docs, but the output for instance_blocks was different than specified (and I marked it as a required field, likely from a copy/paste error). So, thanks for helping us as we are going through endpoints and making them self-documenting.

view more: next ›