They're different and have relative strengths and weaknesses. Despite being a contributor to piefed, I moderate a handful of communities on a lemmy instance and don't really have intentions of moving them. Overall, piefed is a lot less "mature" than lemmy, which makes sense because it is a lot newer of a project. It is getting better now about being more stable, but there are plenty of things that are still changing quite rapidly, especially on the api front.
As for python/pip/typing, I just don't see this as the major issue that some people seem to think it is. We aren't adding dependencies willy-nilly and the framework in which we are working (flask) is a very mature one that has stood the test of time. The fact that python is used for the project has tremendously helped the project in that it has allowed for a large number of contributions from many different people. Frankly, if piefed wasn't in python, it would not be nearly as feature complete as it is now thanks to the wide range of contributions we have received from folks.
Either in this thread or simply by pm works. The blahaj admins have been helpful in trying to debug this, so the most useful thing for me would be the number that is in that url that goes nowhere, 15179 in your example. That is the id of the notification that lets me get more info about it from them.
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.
Alright...I don't have a solution for you, but I am going to try some stuff and see if I can replicate this. After talking with some of the involved admins, I don't really know the problem, but I have some leads to follow up on. I was able to confirm it is related to reports, but why you are the one getting a notification, I am not sure yet.
Out of curiosity, what is one of the urls it is trying to link you to that ends up 404'ing?
Final question, have you reported any posts/communities/users recently?
I am wondering if you are getting a notification that your report was reviewed, but because the content was removed, the link is just 404'ing. I honestly don't know if those kinds of notifications are a thing, but notifications linking to deleted content only to 404 is a known issue that we are working on.
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) -
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.
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!
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.
Are these new notifications you have gotten? Or are they old notifications that now have broken links? It's possible that older notifications that are hanging around in your inbox are lacking all the information that we now include with notifications, so there could be broken links from that.
It looks like blahaj is running a very recent build of the code, so if these are new notifications, it must be something else. It doesn't look like you are a moderator or admin, so you shouldn't be getting reports as notifications. It could be that somewhere in the code it is sending the wrong notification type. There isn't too much else I can help with without getting some lower level information.
@rimu@piefed.social - It would be really helpful tracking this down to figure out what type of notification these are saved in the db as and any other targets saved along with them. A quick search in the code and I don't see any type 20 or 40 notifications where they shouldn't be.
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.
The basic takeaway is that you must have already enabled notifications by clicking the enable button that shows up in that box. Then, since they are enabled, the button doesn't show up any more, so there is just an empty box left. To disable notification, you need to do that through your browser. It's on the list to make this UI a bit clearer at some point.
Edit: This is what it looks like if you don't have notifications enabled
I am using R2 for my instance and I set up those environment variables in my .env file before building the docker container for the first time, and everything just worked. The specifics of different S3 providers can vary a bit. There is a special set of instructions for using Wasabi S3 for example (I think this was contributed by Jerry of feddit.online).
wjs018 @ wjs018 @piefed.wjs018.xyz Posts 0Comments 23Joined 4 wk. ago
This and || inline spoilers || were some of my early contributions to Piefed because I was so frustrated that they weren't in lemmy.