Mobilizon. Your events. Your groups. Your data.
Go behind the scenes of the design of #Mobilizon, our new tool to free your groups and events from Facebook.
(illus CC-By @davidrevoy)
@0 In any case: Thanks a lot for the input. It confirms what I needed and gives some food for thought.
And just in case: we're building already. Nothing shippable or even usable yet: mostly PoCs/research and demos.
If you're curious: current PoC is to find out how AP will integrate in an eventsourced architecture (like Pleroma): https://github.com/Flockingbird/roost/
@CaffeinatedTech Thanks. You refer to the PHP framework, I presume?
Because we are already building the backend and AP engine in Ruby (not rails) so Symphony is not on the table for that, currently.
If I misunderstood and there's a frontend HTML/CSS framework called Symfony, I'm really curious what the URL is.
@0 An Open Source project should leverage the community. Some choices can be made better with imput from others.
But that advice is neither taken as dicate, nor asked on all choices.
E.g. when someone explains to me how to do SEO in 2020, I'll nod, take a note and go with my own choices made on that matter already ;).
And indeed! "getting stuff out" (shipping) is by far the most important. All questions asked are to ensure were shipping the right product and shipping as fast as possible.
@zens I've been using semantic-UI for some courses and love it so far. Thanks for confirming!
Don't know the other two, but'll give them a spin next week. Thanks for your time, also!
@zens I'm a big fan on DHH and his approaches.
Been doing Rails development since before 1.0 :).
Yet for flockingbird I'm using Sinatra: ActiveRecord is just too unfit for our event-sourced (reactive?) use of ActivityPub.
And indeed, JS would be "sprinkled on top of the HTML+CSS" to make it work just a tad smoother or dynamic. Vanilla JS or even jQuery is probably more than enough.
@zens I'm familiar with react, but don't particularly like it. I love redux, though. Also familiar with angular 1; onfortunately.
Haven't used svelte or vue. But all of those are, for this, I guess, overprovisioned. Maybe in some future when we can afford to hire dedicated frontend-devs it will fit.
But even then, serverside rendered HTML will remain of paramount importance; as outlined in previous toot about SEO.
@zens Our most important requirement is not visible: SEO. If privacy preferences allow, we want peoples' profiles to be indexed and ranked high.
That means serverside rendered HTML (with microformatting) is almost a hard requirement. Added benefit is that this makes the app fast, compatible and accessible.
This requirement is so important, that if forms and interactions are too complex to achieve with plain-ol'-HTML forms and a sprinke of JS, i'd prefer redesigning it, so it fits that need.
@zens The goal is to build our entire web-app, but that is far away; and I don't mind switching to something else along the route (react, native, wasm, some other CSS framework).
For now, the direct aim is to build a Proof of Concept and maybe even the MVP. Screens for the far-away goal are on figma: https://www.figma.com/file/CgDIaLgjwVLPzw1ggmrZzy/Flockingbird (work in progress!)
@io I did not yave this on my list yet. It looks really clean and simple. I like that.
It does use some classes, though: e.g. to turn divs into grids; I presume because there's no "semantic" tags for those. But also a.button to turn a link into a button.
I'll certainly look into it, esp. because it advertises with "mobile first".
@bpepple Bulma looks perfect.
I'll look into it, mostly into the accessability. So far: looks exactly what I need. Thanks!
What is currently the most accessible, lightweight (clientside) and simple to implement, HTML+CSS framework for web-apps?
Primarily for a web-app for mobile use.
To be integrated in a fully serverside rendered web-app.
"We moved to GitHub because everyone's already there"
"We shut down the mailing lists because most of our users prefer to use GitLab in their web browser"
"We're rewriting in Rust because we don't really have any non-x86_64 users"
"We're leaving IRC because Discord is more user-friendly"
What all of these arguments have in common is that they exclude people, centralize infrastructure, and eschew free software for proprietary solutions, all in the name of some ill-defined measure of "progress".
@sedcat It was phrased unfortunate. Sorry.
What I meant, was "it is not our *primary* battle", not the most important one. Flockingbird wants to bring "professional social networking" to the fediverse. This is the *one* thing that matters to me/us.
We are not a project who wants to "change the way open source developers work", nor a project who aims to "decentralise software development".
Thats a battle for others to fight, now. Projects like @forgefed, @codeberg, #sr.ht, @gitea or gitlab.
So, did another comparison: Were are all the common fediverse projects at?
Using https://github.com/BasixKOR/awesome-activitypub, turns out that the vast majority is on github.
Se we'll just follow along, for now.
"Choose your battles wisely", the proverb goes. Distributing Open Source software project hosting is not our current battle.
@lps certainly! Limited in amount and limited in length.
And choosable from "commonly used" suggestions (a dropdown) to nudge people to (re-)use existing tags/titles/tags.
Obviously instance owners can deny certain tags, but that is for the admins of that community to decide.
We certainly don't want this (horrible, I might say) instagram-alike hastag-soup.
Hi! We are building a professional social network.
Where you manage your business network. Decentralised, and privacy friendly.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.