You are using piefed, so in the web ui you can click the three dot menu and select the remind me option. This isn’t in the api though, so it wouldn’t be in a third-party app unless they implemented it separately.

Thanks for pointing this out. I am not that active on masto, but I am from the Boston area, so this might be the kick I need to check out that side of the fediverse. I lived in Somerville for 10 years before more recently moving to the burbs. I wouldn’t want to live anywhere else in this country these days.

I’m pretty sure that’s what is happening and I am really looking forward to it.

Yeah this is a bug in the PieFed api. Here is the relevant issue: https://codeberg.org/rimu/pyfedi/issues/1608

Pinging @rimu@piefed.social for help as well.

I don’t think the referer is checked at all for api endpoints, so I doubt that is the issue.

Here you go:

curl --request POST \
  --url https://feddit.online/api/alpha/user/login \
  --header 'Content-Type: application/json' \
  --data '{
  "username": "your_username",
  "password": "your_password"
}'

You can’t register from within Voyager, but you can log in to an existing account (the button on the lower right of the adding an account screen). The reason you can’t register a new piefed account in Voyager is because that functionality doesn’t exist in the API yet.

I was able to log in to feddit just fine using curl, so it seems to be voyager-specific. Not sure if there might be an errant cloudflare challenge or other kind of proxy-level filtering that it might be getting caught up in.

Not sure if @aeharding@vger.social might have suggestions for how to help ID the issue or get a more descriptive error message.

I can confirm that my feddit.online account isn’t working with Voyager for whatever reason. I was able to log in with a couple of other piefed instances without issue.

Tagging @jerry@feddit.online for visibility.

Edit: I just tried Boost and it worked with my feddit account. Could be something really weird going on.

Ah, I see now. I had missed that this was for comments and not posts. I think I can see the bug in the PieFed API. The /comment/list endpoint is fairly complicated due to the way replies can be nested with different hierarchies, and I think it looks like it might not be filtering blocked users at a specific point. I opened an issue in the PieFed repo to keep track of this.

If you go to your blocks on your settings page in the web UI (not in Voyager), are the blocked people listed in the table down near the bottom? I took a quick look through the /post/list endpoint in the PieFed api and it looks like we are filtering blocked users correctly, so I wonder if the issue is that user blocks are not getting created correctly.

Yeah…I don’t consider this a spoiler. This is just a joke, it’s not really significant to the plot at all. Do people consider any frame or panel a spoiler? Really?

Yeah…I think I am going to have to check out Journal with Witch. Too many people in this community have said too many good things about it.

Looks like this is a feature for most markdown parsers. In piefed, the same thing happens. I wrote most of the customizations for parsing markdown, but nothing to create relative links like this except for footnotes. So, it must be the default behavior of the markdown library we are using.

Where are you even seeing this in PieFed? This is a glyph in the feather font that we do use for our symbols, but we don’t actually use that symbol anywhere in the codebase.

The user in question just switched to a different unicode character that looks pretty much identical to the thorn symbol. AFAIK, we didn’t actually get any complaints from Icelanders, but we weren’t happy with the implementation due to its potential impact on that community. At the end of the day, we decided that this is a user problem where bans and blocks should be used instead of putting something explicitly in the code.

Mbin 1.9 just came out and lets users basically set a custom image to go with the link. However, the way it federates is kind of messing up lemmy and piefed, where they just think it is a link to the image only.

Looks like it since it came from fedia. I would need to take a peek at the AP json to be sure when I get a chance. The picture and the link come as two attachments, and PieFed just pulls the first one, the picture.

This was a bug just introduced in the past day or two. Since piefed.zip runs the dev version of the code, it caught it. I just pushed a fix to the code, so piefed.zip will get the fix next time they update.

Speaking for PieFed (I have no idea for lemmy, but I suspect it is in a similar situation), this isn’t something the API currently supports, so Voyager would have no way of knowing the save order of your bookmarks unless it is recording the save times for all the bookmarks you are saving from within the app. However, I just had a bit of a look through the code, and we do record the timestamp of when something is bookmarked, so we can sort that way. It would be a bit of work to include the logic for this, but it seems doable.

I just tried to replicate this and I think there is a bug introduced in the past day or two in the PieFed code. Since piefed.zip is running the development version of the code (as opposed to stable), these kinds of bugs are going to happen from time to time. I will try to work on a fix today.

Edit: the fix was pretty easy. I just pushed an update to the code to fix this, so it will start working again whenever piefed.zip updates (I think they automatically update once per day).