I'll be giving an invited talk at Web Conference in two weeks on social web protocols with a segue to my new credible web group.
In talk abstract I invite folks to join W3C.social . Should be interesting. https://www2018.thewebconf.org/program/w3c-track/
Next meeting of Social Web Community Group (which you're welcome to join) is tomorrow (via mumble). Agenda: https://www.w3.org/wiki/SocialCG/2017-06-07
If anyone knows a service similar to Hetzner's StorageBox, but based in the #USA, please let me know.
basically, I need a few TiB of space accessible via SFTP/WebDAV/NFS/CIFS/whatever that does not cost too much and preferably has no costs per GiB downloaded down the line.
The number of users on Mastodon is stabilizing around 700k users. We've seen only a 10% growth in user count over the last month.
Fewer users are joining us, and some instances are even disappearing from the network.
We don't necessarily *need* growth, though, but remember to keep this place warm, welcoming and open, as new people means new blood, new ideas and more fun 😺
Cheers to all of you !
@Halycon I'm so impressed with your work. I'm wondering how hard it would be to install it side by side with a mastodon instance, on the same domain, with a user settings flag for which UI they get. No need to auth or anything. It looks like the URIs dont overlap except for /. But maybe the URIs should be the same. Hrmmmm.
I thought of a way to deploy this safely. It would also work for the #Mastodon private message problem. In the websub subscription process, the subscriber can included a flag that it implements these extensions. Then hubs can send these extension messages only to appropriate subscribers. Sometimes extensibility points actually work!
I want the fediverse to be much more than microblogging. I want to grow it to decentralize uber, runkeeper, yelp, doodle, youtube, steam, mint, etc. The biggest problem I'm seeing is context collapse: we don't always want to see all this from each other.
A pretty easy solution is opt-in hashtags. A post with one of these is only seen by folks who opt-in. Naive proposal: leading underscore means opt-in. Any reasons that wouldn't work? As an admin, would you be willing to try it with me?
"If Facebook’s a media company, then it’s up to them to dictate the standards of their content. If they’re a tech company, then they need to open themselves to custom frontends.
So, which is it, Facebook?" via dat://pfrazee.hashbase.io/blog/not-media-companies
My new project, I think: build a microblogging-based decentralized meeting scribe tool. All the meeting would be in a reply tree. And the tool would present it like some 2017 version of https://www.w3.org/2013/meeting/sparql/2012-06-26. In v0.2 you'll be able to scribe/comment/vote inside the tool (where it's just posting to your timeline for you). It wouldn't keep any data that wasn't in the timelines of participants, so it's not centralizing.
@maiyannah Is pA a single-page-app like Mastodon, or is the HTML all generated on the server? I see merit to doing it on the server, but in the end I think it makes sense to have a clean separation, with lots of possible UI apps talking to a client API. And have one of those apps pre-render for folks without JS, I suppose.
So, poking more at my problem of how to make a few hundred posts without flooding people, but so they can see them if they want. #Mastodon's algorithm I think lets me do that by 1) start thread with some kind of announcement, 2) quick reply by a bot no one follows, 3) I reply to the bot, 4) then I (and others) keep replying, and the whole chain never shows up in anyone's home timeline (except sometimes maybe). Have I got that right? Is there a better way?
So far, after one day of trying to have two Mastodon accounts, with one being more work-persona, I think I use the wrong persona about 30% of the time, and have no idea which is the right one about 40% of the time. Not promising. I'm sure it would help if I wasn't following the same people, and if I had clear location and/or color distinctions.
And making posts editable, especially so one can add tags one forgot. And making the 500 char limit be advisory (as it really is, given the federation), so there's no reason to leave off tags. I'd suggest "show more" breaks defaulting to 140 and 500 chars, but reader configurable.
A related problem is: why has discussing of Mastodon been driven off Mastodon, to discourse? That clearly shows some flaws in Mastodon, IMHO. One of the stated reasons is people not wanting discussion of Mastodon to crowd out other stuff. I absolutely get that, but we need a different solution, because there will always be topics drowning out other topics. One solution is muting or semimuting tags like #mastodon.
Works at W3C/MIT on Social Web. Grew up in Berkeley, settled in Boston. Father of four. http://hawke.org/sandro
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!