Devs stated it's not a priority but if someone else were to do the work and make a PR, they would not be opposed to including it.
Not invite-only, but invite as an option to bypass the usual manual approval process. Captchas from my experience aren't effective, as PeerTube hCaptchas have been bypassed.
This is different from a forum in that you're explicitly working with a select group of others in a small team to complete a concrete task within a given time window.
Or to put it in simpler terms: for the Summer Season we are looking for developers to both vote on and then work towards completing a two-month long project. This could be fixing a bug or adding a feature to an existing Fediverse project or creating something new.
The benefits to the participant are:
- They're collaborating directly with others who also have an interest in doing whatever is most effective towards growing out the Fediverse. There's a lot of the people in the community who want to help out and see the Fediverse grow, but don't know where to begin. This is meant to be a place where people can pool their efforts and ideas.
- Since we're breaking stuff into two-month sprints, it also is intended to serve as a relatively short-term commitment which can give development experience and give people within the community a chance to know each other.
- Since we're putting what to work on to a vote, this is also an opportunity to put your ideas and input for what is most needed out there, and if you're convincing enough, get others to work on it alongside you.
The benefits to the Fediverse (and free-software as a whole) are:
- Developers are no longer working separately on their own stuff, which is an issue which caused fragmentation. Instead, we're focused on coordinating people's efforts to fixing stuff where it's most needed.
- It helps offload work from central developers or non-profits, which could hopefully serve as a "federated" model of software development long-term if it succeeds.
Let me know if you have further questions.
Yeah, this video is meant to answer the absence of the feature on the desktop site and the official client, explaining the history and the fact that the feature is on the way.
Yeah, this video is meant to answer the absence of the feature on the desktop site and the official client, explaining the history and the fact that the feature is on the way.
Yeah, on a third-party app. This is meant to address the question many users may have of why they don't see the option on the website or the official app itself and explain the history.
I think going multimedia might help, as long as it's under the same brand. I'd say start with a central site similar to how WeDistribute was with articles, then begin linking to places like PeerTube or FunkWhale should we expand out (of course that's very much a long-term consideration). But really it's a matter of getting a central place, content, and the rest can be figured out.
I'm going to be slower responding on here, we also have a Discord bridge if you're good via Discord. I don't get any notifications for Lemmy but Matrix/Discord I do so it's easier to communicate quicker.
Ah, that's really disappointing to see. Communication with Sean has been rather slow but I'll reach out again.
WeDistribute is the one backed by Feneas, so I guess it's the closest to official so to speak. It looks like it's down though. If you do decide to make one, I have some archived issues of a newsletter I periodically run that I can contribute.
Join us on Matrix and we can discuss the specifics: https://matrix.to/#/#collaboration-commons:matrix.org
I think this is a good time to remind people: these sort of opportunities will often present themselves due to a combination of factors well beyond any fediverse user's control. Trying to force them to occur is like trying to build a house out of unpacked sand, it'll quickly fall apart.
What advocates need to do is to focus on building a solid foundation within the Fediverse so that these opportunities can be capitalized on more effectively each time. We don't want it where people join then leave when the hype dies down, when they see a lack of content, or get annoyed with platform quirks. Unfortunately, it seems a lot of discourse tries to focus on marketing-first and assumes the rest will sort itself out. It's the opposite actually.
Relating to the topic at hand though, I agree with Eugen. Direct people to other instances. Do not let mastodon.social's downtime dissuade people. If anything, this might be a good opportunity to spread traffic across instances.
Isn't instance-blocking alone sufficient for being able to prevent the environment from being overrun? I understand the hesitancy to platform reactionaries, but as it stands the network effect is easily the biggest hurdle the Fediverse is going to face. Right-libertarians and actual reactionaries might be a net negative on the main instance, but as far as the software itself goes, numbers are numbers, and could end up making a world of difference.
Let them form their own circlejerks away from everyone else and have slur-blocking be on a per-instance basis, after all that's why the federated design works so well.
man its not even good sci-fi