Neospring v1.14.0

https://neospring.org/@spark/blog/r1.14.0

Neospring v1.15.0

https://neospring.org/@spark/blog/r1.15.0

Big changes in little circle land

Hey,

We're changing circles to no longer receive questions, but instead allow you to post your responses (and general posts) to them through a new tag in the expanded response options!

The ability to post to circles ended up making the code for creating questions and responses unordinarily complicated. On top of that, the profile.html template is the longest and most complicated HTML template in the Rainbeam codebase, and having to maintain it twice was not fun. This resulted in circles often being many stages behind user profiles, creating an incoherent look on the site.

I've decided to repurpose the original "lists" idea which I never finished making and instead turn circles into an organizational feature.

You can still have multiple members in your circles! Only members who are a part of a circle can actually post to them. I'll likely add a button for it at some point in the future, but for now you can copy the circle ID and paste it into the "Circle" field when creating responses to publish them to the circle. For posts, just go to the circle and press the "Post" button!

I know this may be kind of annoying for existing circles users, but this is the best move available for keeping the Rainbeam codebase enjoyable to maintain

For developers: the circles API has been changed to match the general authentication API v0. The only real changes for circles is that /avatar and /banner now use the circle's ID instead of name.

Thanks!

I know what's causing the notifications disappearing thing, so I'll fix that ASAP. I'm not able to reproduce the issue of notifications not being sent when added to a chat, though.

Something to note is that messages seen in the chat window automatically have their notification deleted!

Oh yeah, that's odd. I likely put the position: relative in just the new themes on accident. I did say legacy themes are very likely to break, so this is unfortunately a symptom of using themes that aren't worked on at all anymore.

Will fix ASAP. Fixed.

No. Users under 13 are not of the digital age of consent in the United States (where our servers are hosted).

While Neospring is generally safe, we don’t ask for the age of users and are therefore unable to make sure that their data is not treated the same as that of adults (required by the GDPR)

Please note that digital age of consent is not the same as the age of consent. The digital age of consent is consent in the processing and handling of personal data on the internet, such as IP addresses.

The age of 13 comes from COPPA.

Yeah, I’m going to change how some stuff is designed again soon. Stuff is a little crowded and finicky, the biggest issue is user themes though.

This is intentional as allowing media from anonymous users leads to moderation messes. It can be reconsidered if you get enough people to really want this changed.

“Ask about this” takes you to the author’s profile to create a question asking about that response.

“Quote” allows you to create your own post with that post embedded into it, similar to Twitter.

https://neospring.org/+r/af85377c53

Yeah I’ve been testing it locally all this time and it worked fine, but somehow it doesn’t work on Neospring. I like the idea of having like a choice to still view it, so I’ll likely implement that later today!

It's back up there now since I've pivoted to using floating buttons for quick actions in the bottom right.

I much preferred the bottom bar, but I've decided it's easiest to just leave it at the top ATP since then you only have to write CSS for one platform instead of both desktop and mobile.

Removed

Fixed, sorry!

You've been able to restore the old themes since this update was released. As stated in the update announcement (which has also been at the top of the site for a day), you can use one of the "Legacy" themes in your profile settings.

Fixed

Managed to check your metadata value. The page is failing to parse the JSON data (JSON.parse), which is causing globalThis.update_kv to not register, which is causing you to be unable to save metadata values.

This appears to be caused by "\n\n" in "sparkler:biography"

Fixed, you'll have to manually remove that if it's saved, but it won't be added anymore.

I'll check it out! The link to the image is https://pbs.twimg.com/media/Gb-lNLWbUAAfwHV?format=jpg&name=360x360

That's really odd. I've never been able to reproduce this locally since posts from people you've blocked are hidden in every timeline and can only be seen with a direct link, so I'm not really sure how you've done that

Probably a weird cache thing

.profile_avatar_container {
        width: max-content;
}

.profile_avatar_container::after {
	content: "";
	width: 50px;
	height: 50px;
	bottom: -25px;
	right: -25px;
	display: block;
	position: absolute;
	background-image: url("https://i.postimg.cc/TwxJyWxn/IMG-2596.webp") !important;
	background-size: cover;
}

I get what you're saying, but at the same time nothing has changed besides the position of the navigation bar.

Changing the muscle memory of using the top bar vs a bottom bar could be something, but everything is in the same place also looks the same. The app themes only put the bar on the bottom and make some buttons use a line instead of a filled background.

… {
    right: 100%;
}

That should fully push it onto the right of the element, for example.

Nope, not really. If you want next to your avatar, you could likely set it up in .profile_avatar::after and then just position it.

It’s in the navigation bar now! It’s a little search symbol that’ll show next to notifications.