Please also advise nodes who expect subscribers fill out their About page so folks know who they are, what they stand for (or won't) and why they are different. So many just have the default.
I did the same, plus I wanted to squat a space on The Original for the street-cred ?
Joining an alternate server can depend on price, on site features, but also the value you perceive in their Local feed. I envision libraries, schools, campus groups, clubs etc, local news and municipalities, there's value in a "safe space" all their own or, like some now, by invitation only.
My horoscope said not to wax nostalgic, but I couldn't help reminiscing about the ancient Usenet custom of weekly FAQ postings. Perhaps this might be something that could be built into the #Fediverse servers; they have their info page on the node home, but who ever goes there twice? Or perhaps start folks out subscribed to the node's welcome channel that would send a timed series; once up to speed, folks just unsub!
@az 'agency' can mean many things, from speaking tour authors or vaudeville animal acts to, yes, an Indie label. Book publishers or record labels have a bigger problem of having 'units' to ship, agencies manage bookings.
They have common need to - showcase specific offerings with bios, galleries, news &c - take inquiries into bookings for each - present upcoming engagements for each - publish online and echo to social media
Probably other things too, but that's the minimum.
@miklo this has been the bane of my four decade career, I get an idea but the tech isn't there yet, although it is likely to be there by the time I get to where I really need it! ? Thanks for the tip!
Fishing for some #fediverse advice: I want to build an 'agency' hub for artists where...
- each virtual host has a calendar of events, a contact form, static info pages, photo/video/audio galleries and an rss-equipped blog. - individual accts can have within-host discussions, eg event coordination, planning etc. - accts are by invitation only
Kind of like reinventing #Posterous for #ActivityPub, EVERYTHING about that extinct platform is exactly what I'm after.
@humanetech the bitching about an update is something to endure, but mine does restore tabs, although seems to me that was a config setting somewhere.
I don't get 'snap', and I wonder if flatpack is the same. I had one app depend on a snap-based service, with a potential to have others, but again, on each update, all dependent apps must shut?
I use Linux, and one of the PERKS is only needing a reboot for a kernel fix, and even then it's at my leisure.
What it isn't saying is you need to exit Firefox, THEN sudo snap refresh, and then you can start Firefox and happily use your browser for another week or so before it happens again.
And yes, you can swap it for a non-snap, I found instructions somewhere following an item saying Gnome integration only works with non-snap. Fool that I am, when UbuntuStudio switched to KDE Plasma, I thought I'd retry the snap, but I'm *real* close to swapping it out again.
KDE Plasma crashes, I reboot, and now Firefox starts ... HOWEVER it isn't Firefox as I left it moments ago, it is Firefox as I left it last time I used the deb package, only with fresh imports of bookmarks. History is gone, tabs forgotten, not a big deal, but I do wish there'd been some warning.
Can server owners trade lists of known offenders? Like spam-reports or the kill-lists in Usenet days. Especially for the micro-nodes, it could be tedious for a new operator if they all start with a blank slate.