Skip Navigation

Posts
20
Comments
251
Joined
1 yr. ago

Piefed contributor and part of the piefed.social admin team.

  • Deleted

    Permanently Deleted

    Jump
  • 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.

  • Deleted

    Permanently Deleted

    Jump
  • 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.

  • Even logged in and with filters so that the post is visible, I don't see the post in the piefed community as pinned. Could it have been unpinned when you did your db reload?

    If it is pinned on your side, then it must be a bug of some kind.

  • For really, really poor internet connections, http can be a lot more performant because it has a lot less handshaking that needs to happen. This kind of use case is something rimu cares a lot about since he has previously had to deal with super awful internet connections in the past. It is a very specific use case and outside of that kind of case, it wouldn't be recommended. You can see that both http and https versions of the site can coexist, so it is an option for those that need it.

  • Welcome!

  • In /admin/communities, the far right column has an Edit link. That is where you have some additional settings, including checkboxes that can include/exclude communities from your instance's Popular and All views. You want to make sure that both of these are checked (they are down below the language settings):

  • The pinned posts still obey some of the visibility rules of any other post. So, in this case, piefed.ca has Popular as the default sort on the instance. That means that the community that is home to those posts must have the Posts can be popular box checked in the admin settings for that community:

    I can't confirm that this is the issue, but I was able to confirm with a dev instance that local-pinned posts do show up for anonymous users using the popular sort when that box is checked and don't when it is unchecked.

  • This isn't that far away from mine for two people: ~$600-$700 per month in a HCOL area and doing most of the cooking myself as well. I have found that sizing up a recipe for more people is only a marginal increase in cost. So, cooking for two is not just double that of cooking for one, but less.

  • The thumbtack trick was a game changer for me back when someone shared it with me. I have a dedicated thumbtack in a kitchen drawer now.

  • It took me a minute to figure out how this was a Harry Potter reference. For those also confused, these three magics correspond to the Unforgivable Curses.

  • This series has been super impressive with how consistently funny it has been. Too often I will read a series that is funny for a bit, but the jokes wear out or get too predictable. I still find myself surprised each chapter of this series at how funny it is.

    This chapter, the two jokes that really got me were that Rona's head is full of cats (just like the old internet!) and that death gods are a popular moe trope.

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

  • Lol! That's some timey-wimey stuff! To be frank, I have no idea the exact details of how this little snippet of javascript keeps track of things for this counter. But, unless you are in some kind of hyperbolic time chamber when you browse, I don't think the timer should be going that high.

    Browsing PieFed in real time:

  • Just wanted to quickly acknowledge that we were able to fix this one so quickly thanks to the help from @tenchiken@anarchist.nexus.

    Thanks!

  • Another pleased Bosch owner here. The thing has been solid for about 3 years now since we had to replace an Asko that died.

  • 🤦

    rimu actually fixed the error leading to this and then never actually updated piefed.social with the fix. It should be fixed soon when he comes back online and can apply the fix. I am unfortunately not able to ssh in right now.

  • There are keyword filters that you can create from the filters page of your settings. This is tough because there are so many ways to mention this topic in tons of different contexts. The keyword filters do allow you to make filtered posts still visible, but just semi-transparent so that they aren't as visible.

    Add a keyword filter: https://instance.tld/user/settings/filters/add

  • I'm realizing that we should probably make an easy way to reset the timer on a device if it gets run up due to leaving a tab open and walking away. In the past that timer was nothing more than a curiosity. However, now that there is a way to put self-imposed soft limits on usage, we should flesh out that functionality a bit.

  • @blaze@piefed.zip has been asking for this feature for ages and @Skavau@piefed.social made an issue for it on the codeberg already. The reason this isn't in the api yet is because it isn't anywhere in piefed yet. AFAIK, the read/unread status of comments isn't currently tracked anywhere within piefed. Additionally, for this feature, I don't believe we track the timestamp at which you do interact with a post...so doing something like calculating the number of new comments that have occurred since you last opened that post isn't possible...yet.

    I don't have a great idea of how to do this in a db-efficient way. Keeping track of when every user opens each post sounds like db-query hell. However, there might be clever caching tricks to make it a bit less computationally intense. @rimu@piefed.social would likely have a better idea of how to do this.