I don’t think the people in this thread or others like it are correct in blaming this on PieFed. I just tried to replicate this issue on several different PieFed instances and everything worked as expected. Plus, the other two posts I see about this issue both were made by users from Lemmy instances (slrpnk and db0).

Here is what I tested and everything worked fine:

• Voyager version: 2.49.1
• Android version: 17

Instances tried

just now when I logged in I got the onboarding wizard which for some reason I did not get before

There is a flag saved in the database once you go through the onboarding so that you aren’t shown it a second time. For some time there was a bug that prevented it from showing up at all that was recently fixed. So, some users are seeing it for the first time well after they initially created their account because they were (wrongly) not shown it originally, but it is being properly shown now. After going through it once, you shouldn’t ever see it again though.

it wasn’t me who chose your replied as “prefered” or solution

Community moderators and admins are also able to flag a comment as an answer.

is it possible that cookies & local data from 2 piefed instances interfere with each other?

This is something that is primarily handled by the browser in a session cookie. There shouldn’t be any cross-pollination between domains. FWIW, I currently have 10 PieFed accounts logged in on 10 different instances (plus 3 lemmy accounts and 1 mbin account) and have never had any issue with cookies interfering with each other.

I did a quick peek into the logs and found the server-side error that is hanging things up. I don’t really have the bandwidth to get a quick fix in, but it isn’t anything you are doing wrong. I think rimu should be able to pop a fix in soon.

Funnily enough, it seems like the error is something that can only happen when migrating from piefed -> piefed…the lemmy -> piefed migration path is used a lot more often, so there have been more chances for problems to surface in that scenario.

Yeah, looks like this was an oversight on the API side of the code. I just submitted a PR to fix it.

Hey, I wrote that guide! I’ll try to help simplify it a bit.

tl;dr of creating a basic theme is that all your css changes live in a styles.css file inside your theme’s folder.

Here is what you actually need to do to create a theme:

First, you will need some way to experiment with css yourself to create your theme. That can either be running a development instance where you do your work (relevant guide), or it can be something like running a browser extension that lets you define a custom css to a web page (like stylus that was mentioned in the theming guide).

The actual process of defining what your css should be is kind of tedious. If there is an element on the web page you want to apply styling to, you can right click -> inspect on that element to see the page source for it. That can help inform you about any css classes or an id that might be present on that element to help you write your css selectors. If there is an element where a custom css class would be really helpful, you can either add it yourself if you are going the full local development route by editing the relevant jinja template, or you can ask in the PieFed matrix room for it to get added to the source by somebody else to make your life easier.

I am not really a css expert by any means, but you can reference the css changes that other themes make by browsing the different themes and looking at their styles.css files (link to themes folder).

Once you have a file with all the css changes you want for your theme, the next step would be to get your theme added to the source code. That is where you would reach out to rimu and pass your css to him. He would likely do a QC pass on it before adding it to the main project.

Then, when the next version of PieFed is released and is live, your theme is now part of the project and should be select-able as a community theme! Well done!

Over the past six months, rimu has ~4X more commits to the project than I do, and then it is a steep drop off from there (other than a ton of individual css fixes by travis-jeans). So, it is not entirely a one person show, but it mostly is. Part of that is that rimu is just really quick. We will talk over an idea, and then he will implement it faster than I can even make the git branch.

You are using piefed, so in the web ui you can click the three dot menu and select the remind me option. This isn’t in the api though, so it wouldn’t be in a third-party app unless they implemented it separately.

Nothing to do with federation. piefed.zip decided not to make their modlog public. It’s an admin setting within piefed. IIRC, it isn’t an option in lemmy.

Oh man, give me a scientific issue any day of the week. I would much rather deal with some investigation rather than work on an IND, BLA, or MAA section to submit to an agency. I have tremendous respect for reg folks that can make sense of the agency guidance. Thank you for your service!

I work professionally in the field of pharmaceutical manufacturing, though mainly with liquid and lyophilized presentations. The issue talked about in this video, polymorphism and isomerization, would primarily just be an issue with drugs that are considered small molecules. Historically, that is most drugs…but that is changing as more and more other modalities are hitting the market.

Small molecules, especially in a dry powder, undergo lots of processes that would make cleaning with enough rigor to completely eliminate a polymorph extremely difficult. Things like milling, mixing, spray drying, and pressing are extremely energetic and intentionally disperse powder like crazy. The cleaning cycles for all this equipment are already extremely rigorous, often reducing contaminants to levels too low to measure and then undergoing sterilization cycles with vaporized hydrogen peroxide (VHP) between batches. However, when you are talking about autocatalysis like this, it only takes ppb-level contamination to propagate through the whole batch.

When you are talking about large molecules like biologics (antibodies, most vaccines, etc.), there are a whole bunch of other things that can go wrong, but not this. The most analogous thing I can think of would be a persistent viral contamination. Current good manufacturing practices (cGMP) should be able to alleviate this though, and it wouldn’t impact tech transfer to a different site like what happened in the video. Alternatively, I have worked on mAbs where each batch would measure the glycosylation state because it impacted activity. That is a post-translational modification process for that drug that some batches worked better than others, but we never really tracked down a root cause (before the program was killed).

Another case study that happened on a program I was working on was that we had a series of batches where the active ingredient (a mAb) was oxidized at a much higher rate than normal. Nothing about our process had changed, but it was a clear night/day difference that happened all of a sudden. After lots of testing and ruling things out, we managed to figure out that there were elevated levels of iron in our product. By sampling at each step of our process, we figured out that the iron was being introduced during two steps called bioburden reduction filtration and sterile filtration. You might notice that these are both unit operations where our drug passes through filter membranes (they were in fact the same filters). Ultimately, it turned out that the supplier of our filters had a contamination issue that impacted their filters from a certain lot and later. So, we were ultimately able to fix it, but I remember those reports being literally hundreds of pages of ruling stuff out before we finally figured out the root cause.

Hope that helps you feel better!

Also a former big fan of RIF and I found Boost a fairly easy transition.

There is an admin setting that requires a user to be logged in before viewing pages on the site. We keep that off normally, but we recently had it on for a couple of days because of over-aggressive scrapers.

I just checked in the admin panel and your user isn’t banned. It’s possible that you might be quite unlucky with a VPN exit node or something and are now on an IP that was previously subject to a ban. We tend to not use IP bans except in egregious cases, but those users also tend not to connect via their home connection.

Things you can try:

• Try clearing your browser cache for piefed.social. You want to remove any cookies that might be left in your browser from the site.
• If you are using a VPN try turning it off and clearing your browser cache. Basically trying to start fresh with a new IP address.
• If you aren’t using a VPN, try from a mobile device, third-party app, or one of our alternative frontends (photon, blorp)

Piefed does allow users the option to not federate their votes. So harvesting that data would mean needing local access to the infrastructure or snooping on traffic to/from your local instance.

The final vote came down to a very narrow margin between our top two vote-getters. If you are curious about the very close runner up (that I voted for), that was the opening song from “CITY The Animation” - “Hello” by Furui Riho.

Links:

• anime OP (animated, but edited down to 1:30): https://www.youtube.com/watch?v=10eZAXGuVT4
• Full MV: https://www.youtube.com/watch?v=JxyACq69HgA

It’s a great pick and one of my favorite vocaloid songs. Teto has been blowing up in the past year and Jamie Paige has put out some of Teto’s best stuff.

Just to be clear, I think Skavau is proposing an idea, not talking about a feature that currently exists within PIeFed.

Overall, more fine-grained roles and permissions are a recurring topic that has come up in discussions. That is both among the developers and with other instance admins. I think being able to make some users be able to take some actions like clean up/assign flair or edit wiki pages without being given all the moderator powers would be a big improvement.

The really hard part of this comes when you introduce federation. You both need to give a user the ability to do the thing and also allow other instances to recognize that they have the permission to do that thing, or else their actions will not federate.

Edit: Seems like this is a lemmy problem in general with quotation marks in the spoiler summary block. If you are on a lemmy instance and put this into the markdown, it will render the same way:

::: spoiler "Quotes" get garbled  
That summary above is messed up.  
:::  

So, this isn’t a PieFed issue at all, but something to do with lemmy’s markdown to html conversion improperly url-escaping quotes when it is in a <summary> tag.

Ok, I was really confused about this since I couldn’t reproduce this at all. However, this seems to only apply to quotes that are in a spoiler header. I made a codeberg issue for this.

viewing posts that aren’t in communities

Integrating microblogging more has been a common request in PieFed, but I keep running into this issue whenever I think about it. Posts belonging to a community are so integral to how the whole system works that undoing that is a huge lift.

I don’t know how much of a lift it might be from the UI side when consuming mbin’s API, but at least on the server side, this feature is likely to just be mbin for the foreseeable future.

Follow-up question: I am trying to get a feel for the “international hit” rule and how to apply it in this case. Anime is already a bit of a niche, but it can certainly break out into the mainstream, and I don’t want to contravene the spirit of this event by just choosing something that already hit it big so to speak.

My initial thought for an easy way to gauge this for our community is that videos over a view threshold should be excluded. An arbitrary value might be something like 10M or so. Looking over the award nominees from 2025 in the community for musical piece, that would exclude 3 of the 6 nominees.

Does that seem reasonable?