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.

I really really wish my ISP would get the IPv6 ball rolling. They made a statement that they were rolling it out years ago and then absolutely nothing. Instead I just have to deal with CGNAT. It’s frustrating to have to deal with that despite getting fiber access and speeds.

I agree that it is unlikely to be a chemical reaction. Instead, I suspect you are nucleating bubbles for the dissolved gasses in the solution (think diet coke and mentos).

When yeast is active, it creates CO₂ as a byproduct. This is how you get bubbles on the top of your solution when you are blooming the yeast. This gas byproduct is also dissolved into the water as well. Letting it sit for that long would give it plenty of time to completely saturate the liquid (or even supersaturate it depending on environmental changes).

When you throw the salt in, those salt crystals act as a nice nucleation point allowing those dissolved gases to form a bubble and leave the liquid phase. I can’t really speak to how salt behaves differently to flour in this regard, but nucleation rate is proportional to the available surface area for nucleation, and salt crystals tend to not clump up nearly as much as flour, making more surface area accessible for nucleation.

I suspect you already know this since you make so much bread, but, I was always taught that introducing an osmotic shock like adding salt directly to your yeast will slow down the rising/proofing process. So, it would be best to add the flour, then the salt on top, then mix them together to help blunt the osmotic stress on your yeast.

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).

That makes sense! Thanks for the explanation.

option to filter comment search by instance

Does this mean to search only for comments from users of a specific instance? Or does it mean comments made in communities local to a specific instance? I wasn’t even aware this was in lemmy’s api.

This was the best explanation to date I have seen of what Bonfire actually is. I still think that the ratio of marketing speak to features/users is way too high for me to get excited about it yet. I wish them all the luck and hope for the platform’s continued improvement though.

You are on PieFed, so you can always use a bit of custom css to make them go away. Pop this snippet into the custom css field of your user settings:

.comment_time {
    display: none;
}

TIL Yunohost’s site runs on Flask, just like PieFed! Also, they use TailwindCSS, which is actually really nice. I messed around with it a bit at one point and was a fan.

That explains a lot. I completely forgot about the spiciness factors. I just saw effect in the code and thought it was the instance vote weighting.

100% agreed.

I have contributed quite a bit to the PieFed codebase, but the ActivityPub parts of the code are the main area where I dare not wander unless absolutely needed. Trying to make sense of what AP json should look like for specific actions is basically impossible and each software tends to have slightly different dialects anyway because of the a la carte nature of the FEPs.

To that end, I just saw that you (mbin) just published all of your AP json schema. It is so incredibly helpful to have complete schema in one place for each type of activity. So, thank you a lot! I am sure I will make use of it.

PieFed has the ability for a moderator to restrict votes for all posts within a community to just members, not on a per-post level. Not sure if this is what OP wants.

Also, it is really more of just rejecting and not federating out votes from non-community members. The votes from people on remote lemmy servers would still be counted just on those servers. Federation across servers and software is weird that way sometimes.

My guess is deleted/banned accounts, but I don’t really have a way to confirm that. Even using my admin powers, I still only see the 12 upvotes and 0 downvotes, and none of those have a vote weight different than 1.

I have been digging into the code, trying to look at where the post.score is updated, which has led me to suspect it is deleted accounts (for whatever reason). When a vote happens, the vote is recorded in a table in the database, and the post score is adjusted based on the vote weight based on the voter’s instance (in practice, this is basically always 1). However, when a user is banned/deleted, the votes recorded in the votes table are removed, but the post score is not adjusted accordingly to account for the now-deleted votes. The score just stays that number saved in the post table of the db.

@rimu@piefed.social - do you have any more insight? I was trying to think of the possibility of duplicate vote actions both contributing to the score, but I don’t think that should happen. I can’t really think of what else could make the score so out of line with the votes.

€30,000! I was stunned when I just pulled up their crowdfunding campaign. Apparently that is enough money for software “maintenance”. I think you have severely underpaid me for my contributions to PieFed if that is the going rate. I was just a sucker doing it for free. 😜