Yeah, I think this fell victim to some url cleaning that PieFed does. Playlists must not get posted too often for this to just be found now as this section of the code has stayed relatively unchanged for a while. Thanks for bringing it to our attention!
@rimu@piefed.social - it looks like the playlist url structure is not playing nice with the fixup_url function ref.
Just an update on this front, server load is stable right now as I type this after rimu did some stuff on the server to help. It’s pretty clear this was a DDOS and not a rogue AI scraper because it was hitting the same url many times a second instead of crawling tons of urls like a scraper bot would.
We’ll keep an eye on things. Thanks for your patience.
I think that is a separate use case. This request is if you are actively browsing an instance you don’t have an account in, but want to join a community, to have it redirect back to an instance you do have an account on.
Edit: I guess it is kind of both issues.
If this is cloudflare, then it is likely that cloudflare is thinking that the browser is a bot of some kind. @rimu@piefed.social is going to have to take a look at tweaking the CF configuration.
Hard to say. The fact that this is a cloudflare issue and not some kind of exception from within the code makes it more possible. If it was just a code exception on PieFed’s end, then it would have been unlikely because authentication via the API and the web UI are completely separate code paths and work differently.
It seems like your issues with feddit.online happen downstream of cloudflare though. The issue with feddit.online has me genuinely stumped and I wonder if it isn’t app-specific in some way (user-agent maybe?).
This is already the case. Each instance sets their own trusted instances. There are no instances trusted by default. In /admin/instances if you click edit in an instance’s row, then you can check the box that it is a trusted instance. Also, these are one-sided relationships. Instance A can mark Instance B as trusted, but the converse is not required.
Something like that could be a good place to utilize “trusted instances.” So, instead of just choosing a random instance of all of the piefediverse, it chooses a random trusted instance.
The feedback in this thread overall has been helpful.
Some instances have used it to do something like a dynamic message of the day. That is the most I have seen it used for so far.
Edit: See the top of the main content pane of anarchist.nexus as an example.
Previous threads about these filters were people complaining about them being hardcoded, completely ignoring that they are completely optional and off by default. It would go something like this:
Look at this awful thing PieFed does!
def do_the_thing():
# relatively simple code that does the thing
It completely ignored the context that the do_the_thing function is only called if the admin wants to do the thing.
They’re just making shit up. In their mind I guess Javascript that is intentionally included by an admin to customize their instance counts as ACE. In that sense any webserver you ever browse to is capable of ACE.
arbitrary
You mean the Javascript that would need to be written and added by the instance admin? Something that any admin with infra access could do anyway? Hardly seems arbitrary at all. ACE usually means something not intended.
There have been quite a number of changes recently to how deleted content is handled, so it looks like the menu content might have been an oversight in that. I will make an issue on codeberg for this when I get a chance. Thanks for the report!
IIRC, the crosspost button only shows up on link posts (like links to an article or something). I remember trying to add that to image posts in the past and ran into some kind of issue, but it’s been a while and I don’t remember exactly what the problem was. There is an open issue about this.
I’m sure you will be pleased to know that the filter this post is about and most of the others mentioned in this thread are, in fact, off by default.
It’s also a checkbox on the admin/misc settings to make it easier to disable.
It’s listed under the account dropdown menu of the navbar (Bookmarks). If you are on a smaller screen, it will be collapsed into a hamburger menu in the upper right.
I know the blocking stuff is actively being worked on as we aren’t happy with it yet. However, that is an issue where it would be literally impossible for every user to be happy with whatever end state it results in. That is an area where the different software platforms can offer people different experiences so that they can seek out the type of experience they are looking for.
Almost everything else you listed here can be turned on/off by an admin. I didn’t know about the 8-character username thing, probably worth revisiting that. The downvotes being disabled with low attitude is one I don’t see being removed, but could be an admin-set threshold (or disabled) in a future version. In fact, I suspect that the formula was written this way to make the threshold more well bounded instead of a simple up - down calculation.
If you are seeing those on lemmy or in a different client than the web ui, that would have to be something else. The red triangles don’t federate at all, nor are they in the api, they are just based on the local content of a user on that instance.
the whole þ fiasco
That has since been removed. Yeah, rimu is certainly opinionated and passionate about what he believes in, but has also been pretty receptive to feedback, both from users and from admins (like in the private voting case). Fortunately, there are alternative threadiverse platforms out there for people that want them. Both lemmy and mbin do some stuff better than PieFed, and that’s ok. The different projects have maintained working relationships at the dev level to try to make sure interoperability outside the base activitypub spec doesn’t completely break (the post-moving feature/FEP was a collaboration between PieFed, lemmy, and NodeBB for example).
You were really close, you need to hide the outer container that the
.message_reactionis in. Here you go:.message_reactions { display: none; }