Piefed contributor and part of the piefed.social admin team.
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.
When you add the image to the post, it is uploaded to the server and has a url at that point. So, you should be safe to remove images from your phone.
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.
Actually no. I just had a look through the code and we have some pretty descriptive error messages depending on how it is failing:
@demigodrick@piefed.zip might be able to help you better as your local admin.
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.
It’s just an option available to an admin. Different instances can have different use cases and goals.
An example is that earlier in PieFed’s development, there was a schoolteacher that was experimenting with using PieFed as a forum for the class. This would have primarily been just a local forum with no/minimal federation. In a setting like that, having a public modlog would essentially mean having a log of every classmate’s transgressions and punishments (at least with regards to content). This isn’t necessarily something that would be desirable in a more school-like setting.
As for .zip’s decision not to have a public modlog, it doesn’t really make that much of a difference since they are so heavily federated to other instances that do have public modlogs. The modlog actions are federated similar to content.
You don’t need to use one of these apps. PieFed is perfectly capable of running in a browser, even a mobile browser. Also, you can install PieFed on your phone as a PWA (progressive web application) so that it can be run on your phone exactly like an app.
Some people prefer a different interface though, so these other apps provide options for them. Also, some people are making a transition from lemmy and these apps generally also support lemmy, so it makes the transition easier when the interface stays the same through the transition.
€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. 😜
pre-blocked instances
Again, this is up to your local admin. Each instance is going to be run differently. The .zip instances (lemmy and piefed are run by the same team) tend to be a bit more open with their defed/block policies compared to some others. I can only really speak about piefed.social for which I am an admin.
Something to note here is that there are two different things going on. The first is user-level instance blocks like you mentioned here. They are removable by the user, and are a kind of softer way of blocking things compared to the second method - defederation. When an instance is defederated, then it is server-wide and the user can’t see content from that instance no matter what their settings are. You can review the defederated instances set by the .zip team on their instances page.
modlog is empty
This means that the .zip admin team has decided not to make the modlog public. One of the settings available to a PieFed admin is to toggle whether the modlog should be accessible to non-admins or not. Other PieFed instances might have a public modlog. On piefed.social for example, you should be able to view the modlog even without an account.
How old does my account have to be to make a community?
An account needs to be at least 24 hours old to make a community in PieFed (or be an admin). This is for spam prevention. There isn’t a reputation requirement for community creation, that page is just what we redirect to for multiple different things, so it is a bit of a broad message.
Is there a way to separate upvotes and downvotes?
I don’t think this is possible in the default web UI. It probably is possible in some apps or alternative frontends. If you hover over the number, it will pop up with the number of up and down votes. There might be some custom css you can apply in your profile to make them show up separately, but I am not good enough at css to tell you what that is.
Why are instances blocked by default
This is purely controlled by your instance admin. PieFed does ship with a default list of defederated instances, but it isn’t baked into the code or anything. It is entirely customizable by admins after the software is set up.
why can’t I see the modlog?
Links to the modlog are in several places:
Something about this feature @rimu@piefed.social is showing off is that it is only doing the link substitution in the web frontend. Any links in posts/comments will remain unchanged in the API that clients like blorp and voyager. This lets the different clients deal with this as they would like.
It might be possible to do this substitution on PieFed’s side for API responses, but I think it should not be the default. We would need some way for an API client to indicate that this is what would be desired.
For removing the bottom bar, use the css from this post in your user custom css: https://piefed.social/post/1278887
Yeah, I see what you are talking about. I think probably just a list below the cloud would be easy enough to add. The list that is in the sidebar is limited to the 30 most used in that community (iirc), but there isn’t any reason we couldn’t list more if a user clicks through wanting to see the tags specifically.
I believe @mrkaplan@piefed.world is working on it. They just completed the upgrade to 1.2 within the past week and are working on the 1.3 upgrade process. They customize the code to some degree and run a FHF branch of PieFed, so it takes a bit of time for them to finish that process and test it.
That makes sense! Thanks for the explanation.