11 Followers
83 Following
456 Posts

Software developer here to learn about tech, especially the future of social networking. Certainly not an expert on any of it -- I have much to learn. Username is more aspirational than it is descriptive.

I tend to take long breaks between posting because of the way I am.

(Ridiculous pic is from when I needed a sample image for a test and maxed out my artistic skills.)

Every single argument people make about Apple needing to tax developers to be on iOS can be answered by saying.

Ok. But the Mac. And Windows.

You have to ignore 20+ years of computer history to justify Apple's arguments.

I find it so weird people suddenly act like macOS and Windows just don't exist when talking about iOS app distribution.

All these ridiculous arguments saying Apple deserves to tax developers whatever they want and the ecosystem can't possibly exist without the AppStore.

Because indie macOS apps have never existed?
Because downloading a Windows app from a developers website is not a thing that has ever existed?

Because no software ever existed before the AppStore?!?

I hope everyone is on board with the idea that, one day, social media - of pretty much every kind - is going to be a lot more peer-to-peer than it is today.

Given that - are folks having conversations about what moderation and community delineation looks like in that context? Let's imagine it was one-click and free to spin up a Fediverse instance - what would need to change about our approach to moderation? Can we do that today, so we're ready, at least conceptually, in the future?

Folks, i'm still looking for work -- either freelance or FTE.

I'm a full-stack web developer with a focus on PHP CMS-based systems (mostly CraftCMS and ExpresionEngine, some Wordpress, a smattering of Drupal). Also on the back-end: Laravel, Symfony, some Yii. On the JS side, i do mostly vanilla JS, some Vue and other smaller/less-intrusive frameworks (please don't make me do React!) I also write solid, semantic, accessible markup and CSS (by hand) and care deeply about accessibility in general. I'm also a fiend for content architecture and i love SQL!

If any of this sounds like a match for any project or opportunity you've got in mind, PLEASE let me know!

#FediHire #CraftCMS #Laravel

i wish everynyan who unironically uses ā€œi18nā€, ā€œl10nā€, and ā€œa11yā€ a very stop fucking abbreviating accessibility related words you fucks
 Mike Macgirvin šŸ–„ļø wrote the following post Fri, 12 Jan 2024 14:38:02 -0800 A brief overview of the streams repository.
The streams repository is a fediverse server with a long history. It began in 2010 as a decentralised Facebook alternative called Mistpark. It has gone through a number of twists and turns in its long journey of providing federated communications. The fediverse servers Friendica and Hubzilla are early branches of this repository.

The first thing to be aware of when discussing the streams repository is that it has no brand or brand identity. None. The name is the name of a code repository. Hence "the streams repository". It isn't a product. It's just a collection of code which implements a fediverse server that does some really cool stuff. There is no flagship instance. There is no mascot. In fact all brand information has been removed. You are free to release it under your own brand. Whatever you decide to call your instance of the software is the only brand you'll see. The software is in the public domain to the extent permissable by law.  There is no license.

If you look for the streams repository in a list of popular fediverse servers, you won't find it. We're not big on tracking and other spyware. Nobody knows how many instances there are or how many Monthly Active Users there are. These things are probably important to corporations considering takeover targets. They aren't so important to people sharing things with friends and family.

Due to its origins as a Facebook alternative, the software has a completely different focus than those fediverse projects modelled after Twitter/X. Everything is built around the use of permissions and the resulting online safety that permissions-based systems provide. Comment controls are built-in. Uploaded media and document libraries are built-in and media access can be restricted with fine-grained permissions - as can your posts. Groups are built-in. "Circles" are built-in. Events are built-in. Search and search permissions? Yup. Built-in also. It's based on Opensearch. You can even search from your browser and find anything you have permission to search for.  Spam is practically non-existent. Online harrassment and abuse are likewise almost non-existent. Moderation is a built-in capability. If you're not sure about a new contact, set them to moderated, and you'll have a chance to approve all of their comments to your posts before those comments are shared with your true friends and family. For many fediverse projects, the only way to control this kind of abusive behaviour is through blocking individuals or entire websites. The streams repository offers this ability as well. You'll just find that you hardly ever need to use it.

Because federated social media is a different model of communications based on decentralisation, cross-domain single sign-on is also built-in. All of the streams instances interact cooperatively to provide what looks like one huge instance to anybody using it - even though it consists of hundreds of instances of all sizes.

Nomadic identity is built-in. You can clone your identity to another instance and we will keep them in sync to the best of our ability. If one server goes down, no big deal. Use the other. If it comes back up again, you can go back. If it stays down forever, no big deal. All of your friends and all your content are available on any of your cloned instances.  So are your photos and videos, and so are your permission settings. If you made a video of the kids to share with grandma (and nobody else), grandma can still see the video no matter what instance she accesses it from. Nobody else can.

Choose from our library of custom filters and algorithms if you need better control of the stuff that lands in your stream. By default, your conversations are restricted to your friends and are not public. You can change this if you want, but this is the most sensible default for a safe online experience.

There are no inherent limits to the length of posts or the number of photos/videos you can attach or really any limits at all. You can just share stuff without concerning yourself with any of these arbitrary limitations.

Need an app? Just visit a website running the streams repository code and and install it from your browser.  

Nobody is trying to sell you this software or aggressively convince you to use it. What we're trying to do is show you through our own actions and example that are more sensible ways to create federated social networks than what you've probably experienced.

You can find us at https://codeberg.org/streams/streams

A support group is provided at @[email protected]

Have a wonderful day.
@[email protected]
A brief overview of the streams repository.

The streams repository is a fediverse server with a long history. It began in 2010 as a decentralised Facebook alternative called Mistpark. It has gone through a number of twists and turns in its long journey of providing federated communications. The fediverse servers Friendica and Hubzilla are...

Really? They called it visionOS and not eyeOS?

You know all the random unforced tech layoffs are just labor disorganizing, right?

That's it. That's all they are. They're making us play musical chairs with our jobs to keep us from ever building enough trust to organize. Their ideal outcome is a labor pool that's too traumatized and reactive to act collectively.

Just pushing everyone into a scarcity mindset on purpose. It's the whole US economy writ small.

If you liked that toot then you'll love this book
https://abookapart.com/products/you-deserve-a-tech-union

You Deserve a Tech Union

Hello! I have just been laid off as part of Google's second annual mass lay off. If your team is looking for an experienced developer do let me know. I work remote, and am an expert in accessibility, web development, and Android (Java/kotlin). I do iOS (swift/objc) as well, and do have backend experience. In general looking for low stress teams; already had my share of unreasonable work at Google.
Hey people who know more than I do about #coop structures, what are the pros and cons of worker-owned vs customer-owned? Are there mixed models? I have some of my own opinions but am very curious what others have to say about it.