wjs018

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.

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;
}

€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. 😜

I can confirm that this is something @[email protected] has brought up in the past on multiple occasions. It’s an issue that I am sympathetic to, but so far it hasn’t been a high priority for us to take the time to try to address. One of the biggest complaints we see people have about the threadiverse in general is that there isn’t enough content; that their feed gets stale too quickly. So, having more subscriptions hasn’t necessarily been seen as too much of a “problem” from my perspective.

What I did work on was making it easier to unsubscribe from communities. If you filter the communities page to just communities you are subscribed to, it should be a simple matter of clicking the buttons to unsubscribe to undesired communities. It used to reload the page each time, which made that task immensely tedious.

Frankly, now that Skavau has a third party backing up their position, they will be insufferable about it until we try to fix it 😜

The ~ symbol is how you prefix a feed in piefed. Just like you use an @ for users and a ! for communities.

I run a personal lemmy instance and two personal piefed instances, so I was just doing some comparisons. My instances are mainly used for development and testing, so they are only subscribed to a handful of communities and just have one active user.

You are correct that when it comes to performance, like snappiness and responsiveness, the database is probably going to be the bottleneck. Unless you are scaling up to a huge degree, I would be surprised to see meaningful differences in the number of requests that could be handled due to language differences between rust and python. Yes, python is an interpreted language, but most of the libraries you are using are basically calling other system libraries written in a language like C, and the program can execute way faster than your database I/O can give it data to process anyway.

Here is my usage summary. The lemmy instance has been running for about 1.5 years while the piefed instance has been running for just shy of a year now. I have only included the memory usage and disk since I don’t think either is really CPU hungry or bound in my use case.

I didn’t remember that! I have just watched the anime rather than read the manga, but I remember really liking the show…right up until the end of the second season.

Not to worry, Ubuntu is just one of many choices…

More people need to make use of the curation tools available to them in my opinion. Too often I see people browsing /all and then complain about seeing tons of stuff that they don’t like. There are tools that are available to them to help them create a more pleasant experience that they just aren’t using. The fediverse doesn’t have some algorithm that learns the type of content that you most often engage with and feed it to you, you have to more proactively do the curation yourself.

Just as an example, I was in a conversation with one of the lemmy.world admins a while back. We were talking about instance blocks and how infrequently users actually use them. Across all of the users on lemmy.world, only about 700 of them actually created an instance block for the most-blocked instance (lemmynsfw). Only two instances had more than 500 users block it.

In Skavau’s defense, they aren’t a programmer, but are probably one of the most active people on piefed’s chat server/matrix room as well as the codeberg repo providing ideas and feedback. So they are volunteering time that way (in addition to being site staff for piefed.social).

Some of the ideas in this post are good imo, but are currently not possible yet using the piefed api due to it being much less complete compared to lemmy’s. So, it helps us figure out prioritization on what kinds of endpoints would be useful to flesh out next.

As somebody that has made contributions to improve the PWA responsiveness, the difference between touch and cursor controls can be tough sometimes. The css framework we use (bootstrap) generally handles it well, but the pop-ups are one area where I’m not really happy with it, but I don’t have a better solution yet.

I just want to point out here that this blog post is old at this point (published February 2024). I believe that mbin in particular has made improvements in this regard. Also, we have added some features to piefed, and introduced a little bit of new Javascript/css. I am not sure exactly how this would compare today.