One of the most surprising reasons that people have told me that they dropped off the Fediverse is that they simply forget which server they signed up for.
-
One of the most surprising reasons that people have told me that they dropped off the Fediverse is that they simply forget which server they signed up for.
@evan I get it, if there is a big "umbrella brand", like Mastodon in your head and you've signed up for "bobscoolserver.social" it's easy to see how you could loose track of that.
We're looking at onboarding now for the next release (4.6) and we're looking at little things we could do to help people, e.g. a cleaner welcome email getting them to follow a few more folks more quickly. The current email is fine, just likely a bit overwhelming for some.
Looking for additional suggestions?
-
One of the most surprising reasons that people have told me that they dropped off the Fediverse is that they simply forget which server they signed up for.
Questo post è eliminato! -
@evan I get it, if there is a big "umbrella brand", like Mastodon in your head and you've signed up for "bobscoolserver.social" it's easy to see how you could loose track of that.
We're looking at onboarding now for the next release (4.6) and we're looking at little things we could do to help people, e.g. a cleaner welcome email getting them to follow a few more folks more quickly. The current email is fine, just likely a bit overwhelming for some.
Looking for additional suggestions?
@scottjenson It might be as easy as offering to save a bookmark after onboarding?
-
@scottjenson It might be as easy as offering to save a bookmark after onboarding?
@evan @general @scottjenson maybe some kind of periodic email from the instance? Or is that too spammy? 😅
-
@evan @general @scottjenson maybe some kind of periodic email from the instance? Or is that too spammy? 😅
@quaff @general @scottjenson drip emails are pretty much the standard in commercial social networks, though. "Now that you're on Mastodon, follow these great hashtags..."
-
@quaff @general @scottjenson drip emails are pretty much the standard in commercial social networks, though. "Now that you're on Mastodon, follow these great hashtags..."
evan@cosocial.ca daily digests!
-
@julian does NodeBB do any retention emails?
-
@julian does NodeBB do any retention emails?
evan@cosocial.ca we do, yes. The default settings are to not spam the user, because I personally dislike getting emails I didn't explicitly sign up for.
Those defaults can be updated by the site admin for all users, or changed by the local user on a profile-by-profile basis.
NodeBB has daily/weekly/monthly digests, and can send emails for all of these events:
-
@evan I get it, if there is a big "umbrella brand", like Mastodon in your head and you've signed up for "bobscoolserver.social" it's easy to see how you could loose track of that.
We're looking at onboarding now for the next release (4.6) and we're looking at little things we could do to help people, e.g. a cleaner welcome email getting them to follow a few more folks more quickly. The current email is fine, just likely a bit overwhelming for some.
Looking for additional suggestions?
scottjenson@social.coop It might be a good idea to make the site that you're on a lot more clearly visible at all times instead of just dropping you to a very agnostic Mastodon interface. I've noticed that people get confused because "Mastodon" can refer to too many things (the software, as an alternate term for the fediverse, the site itself) so they just sort of fall off. I think some level of persistent site-wide branding (not just a banner on the side of the screen!) will go a long way. Maybe even make it easier for sysops to theme their instance and encourage it? Just spitballing here
-
@julian Wow, that's great!
-
scottjenson@social.coop It might be a good idea to make the site that you're on a lot more clearly visible at all times instead of just dropping you to a very agnostic Mastodon interface. I've noticed that people get confused because "Mastodon" can refer to too many things (the software, as an alternate term for the fediverse, the site itself) so they just sort of fall off. I think some level of persistent site-wide branding (not just a banner on the side of the screen!) will go a long way. Maybe even make it easier for sysops to theme their instance and encourage it? Just spitballing here
Theming is huge... it was one of our priorities after (or around the same time as) building out a plugin system.
The ability for admins to easily drop in CSS to differentiate their sites without having to spin up an IDE is quite important.
-
Theming is huge... it was one of our priorities after (or around the same time as) building out a plugin system.
The ability for admins to easily drop in CSS to differentiate their sites without having to spin up an IDE is quite important.
@julian These are all great ideas, thanks. I've noticed several instances do significant theme adjustments (looking at Hachyderm.io as an an example) That doesn't mean it's EASY, just that it's proof that people want it.
Making something themeable in an easy way is not a simple engineering task however as you never offer exactly what someone wants. However, I do think a few simple things like colors and banners would go a long way.
-
@julian These are all great ideas, thanks. I've noticed several instances do significant theme adjustments (looking at Hachyderm.io as an an example) That doesn't mean it's EASY, just that it's proof that people want it.
Making something themeable in an easy way is not a simple engineering task however as you never offer exactly what someone wants. However, I do think a few simple things like colors and banners would go a long way.
scottjenson@social.coop true, although I will say from experience that there are levels to how much people are willing to customize their instance.
Speaking from 10+ years of NodeBB (which didn't federate for nearly all of it, so keep that in mind), admins are able to, in order of difficulty:
- pick a bootswatch skin (this instance I am on uses the "Brite" bootswatch skin)
- drop in any amount of CSS to override anything
- drop in any amount of SCSS if that's your jam
- drop in any amount of javascript that is run after everything else is done
- change/override bootstrap's
variables.scss(this instance I am on overrides the primary colour from a bright green to the ActivityPub pink) - create your own customized theme to change absolutely everything about the site including templates, js, css)
Those first two are the biggest ones due to their ease of adoption, and overlaying additional CSS doesn't require too much engineering effort, although I am speaking in hindsight.
Also, you'd be surprised what people can do if given a textbox and told to write their own CSS. ha!
-
@julian My understanding is that most of the things you list from CSS onwards is already possible with Mastodon (It's how Hachyderm.io does it's custom CSS)
I do think "adding a theme" is a reasonable request
-
@julian My understanding is that most of the things you list from CSS onwards is already possible with Mastodon (It's how Hachyderm.io does it's custom CSS)
I do think "adding a theme" is a reasonable request
@scottjenson @julian@activitypub.space Apparently the process of adding a custom theme to the current Mastodon theme selector isn't *too* much of a coding effort: https://github.com/ronilaukkarinen/mastodon-bird-ui?tab=readme-ov-file#make-mastodon-bird-ui-as-optional-by-integrating-it-as-site-theme-in-settings-for-all-users
Bird UI and Tangerine UI are the two well-maintained Mastodon themes I know of, although I assume they're mostly (all?) just CSS without touching any templates. Letting server admins install themes of this kind by drag & dropping a zip file could be a nice dev target.
-
@scottjenson @julian@activitypub.space Apparently the process of adding a custom theme to the current Mastodon theme selector isn't *too* much of a coding effort: https://github.com/ronilaukkarinen/mastodon-bird-ui?tab=readme-ov-file#make-mastodon-bird-ui-as-optional-by-integrating-it-as-site-theme-in-settings-for-all-users
Bird UI and Tangerine UI are the two well-maintained Mastodon themes I know of, although I assume they're mostly (all?) just CSS without touching any templates. Letting server admins install themes of this kind by drag & dropping a zip file could be a nice dev target.
julian@fietkau.social exactly. As you progress from simple CSS overrides and onwards, it gets exponentially more difficult.
CSS overrides fix one or a few elements, SCSS fixes a bunch of elements, neither touches the actual structure of the page, but opening up layout and template editing raises the bar considerably.
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@ElManga io voglio fare una serata con te, assolutamente 😉
-
GLOBAL NEWSWIRE: Gaza Influencer Malak Fadda Leaves Strip Amid Uproar
https://x.com/GetTheDailyDirt/status/1969109092401644005
GAZA: Influencer Malak Fadda faces accusations of hypocrisy after departing the Strip, sparking an online storm.
CRITICS: Cite past vows from Malak Fadda never to leave and substantial aid fundraising.
A prominent Gaza influencer, Malak Fadda, has ignited a fierce online storm after her recent departure from the Strip, sparking widespread accusations of hypocrisy and financial impropriety.....
-
@misty it would still be better than a total loss, but still catastrophically incomplete.
I can envision this being fixable with some kind of “object move” that servers recognize so that they can edit the in-reply-to etc to keep threads intact, even though plain URLs inside would still be broken.
Or maybe we need some other kind of “global derefernceable IDs” for the objects? Do the FEPs for nomadic identities support something like that?
2/2
-
@francina1909 sono tornato strisciando, ma ce l'ho fatta.
-
right on!
-
@ElManga grazie tesoro 😘
Ti sei ripreso dalla Passerina (quella alcolica)?
-
@misty I've been thinking about this since my first server change, and what I realized is that the biggest obstacle to this isn't even Mastodon's lack of support for it, but a huge limitation in the ActivityPub protocol itself: objects IDs must be “a publicly dereferenceable URIs [...] with their authority belonging to that of the originating server”. So even if the content would be copied over, all threads and references would still become invalid 8-(
1/?
-
@francina1909 Uellà! Auguri! Un abbraccione
