😢

You better win something.

Oh yeah I need to do relationship checks for reactions still (going to do it today!)

Fixed now!

Perfect

Well, that's what it's for! No stupid limit on blocking, so go wild. Hope you are able to get it working. I'll admit the blocking system is far from perfect, but it works good enough in testing, so hopefully this fixes things for you.

All of your blocks are using the old system, which doesn't work with timeline blocking. Blocks were fixed to correctly set the user when blocking (happened about a month ago).

This image is what your (admin) blocks page looks like:

Notice all the blocks are inbound to yourself. This is because they're legacy blocks which didn't place user IDs properly.

This is what the block page should look like:

Delete all these blocks manually and then redo them (annoying I know, there was no other way though) and it should work properly.

I've checked the other users who commented before me here and it is the same case.

Fixed, thank you!

It should be working fine, you may need to clear your cache or just hard refresh the page.

No, no! No irritation, no need to feel bad.

I was just in the middle of working on some other things and I might've come out a little mean there, but I promise everything is fine! Sorry to make you worry.

That's unfortunately where this is at. People don't seem to understand that a screen reader also cannot read an empty space. The person who sent the original question has a valid complaint, but I've seen many more people complain about this and use accessibility as an excuse because they just want an empty username to look cool or something.

You may need to clear your cache! Nothing has really changed at all (round buttons, slightly more round icons, different icons in some places where the icon didn't make any sense).

All CSS served on the site is minified during the build step using LightningCSS.

This build step is mainly there to compile JSX (even though there is no JSX yet) with swc, but I figured I might as well minify the CSS while I'm there.

Ah, very sorry, it really should be. This will be updated ASAP to clarify!

In Europe, for example, the digital age of consent is 16 years old. In Asia, it varies heavily by country. 13 is our base because our servers are hosted in the US, so all internet laws there apply to Neospring and its users.

Yes. It's always just been CSS.

Yes! I'll add it as an alternative option at some point in the future.

It's easier to replace everything in the file that was :is(.app *) with :not(.legacy *) than it is to invert the styles.

Fixed the font thing.

You may need to clear your browser cache or try a private window.

You may need to mark your custom CSS changes as !important!

Side note: some of the settings in your account settings don't give you a message because they're local settings

Ah I see the problem. The navigation bar on the top if overflowing, meaning this only affects the old light/dark themes. App themes are not impacted by this, since the navigation bar is properly designed for mobile.

The fix for this is migrating profiles to the app themes, or just bringing the app mobile nav to the normal themes. Only issue is the redesign looks stupid with the navigation on the top, since the fix is putting the text below the icons (making it look like a proper mobile navigation, which is always on the bottom)

overflow-x: hidden is not an option here because it breaks some weird CSS things

Sure! I just need to look at it myself to figure this one out.

The app theme contains the new bottom nav. Switch to one of the regular 3 themes to remove it.

Reverted and moved to secondary themes https://neospring.org/+r/cfc07b255a

Yeah, this is unfortunately the best way to do it though. You've always been able to quote things this way (the "Follow-up" button has always used this), but I've changed the way they look now because it was needed to improve performance.

When we pulled responses previously, we did this:

if reply.is_empty() {
    None
} else {
    match Box::pin(self.get_response(reply, recurse)).await {
        Ok(r) => Some(Box::new((r.0, r.1, r.2, r.3))),
        Err(_) => None,
    }
},

Since we render everything on the server, this quickly stacked up to a page containing 50 responses ending up with 100 responses. For every single response, we also fetch the author and its question (+ the question's author) if applicable. This means we were running over 200 SQL queries to load a single 50 response page.

This quickly tanked performance on profiles which uses "Follow-up" a lot, leading to >1500ms load times.

Since I've been splitting the templates/ directory into using "partials" (sub templates which are just a single component), I decided to add a partial for rendering responses:

https://neospring.org/_app/components/response.html?id=7418214140306cbe06159b5770b62a853bfc09ed2deafe0d778f1b5392e0c15e&do_render_nested=false

(Note this is the same way chat messages are rendered! We still render everything on the server, just at different times now.)

The has taken load times on such heavy profiles from 1s+ to around 400ms on average. I had to change the template for follow-ups because:

1. I didn't really like it, I think the Twitter-like format looks a little better (although it can still be cleaned a little more here to make it more visually obvious)
2. Everything is loaded through the include-partial custom element, which is like an iframe if it didn't use ShadowDOM. It's much easier to make a clean HTML template using this instead of the other solution

Anyway, hope that helps explain some things! Forum-style quoting has also been mostly supported, though, since that's mainly just on the Markdown parser (except for the interactions).

Refresh twice on Safari IOS. Not sure for Android, but clearing cache will always work!