What og your mailbox looked like this https://www.yourtempo.co/ - non-persuasive design
8 new photos in "FuckOffGoogle Street View" #UrbanArt gallery:
Mostly taken during Saturday's protest against #Google, a projected "Google campus" and start-up-ification of our neighborhoods.
After a 2 week break, the Joy of Coding is BACK today with Episode 148! I'm going to be digging into a mysterious session store bug, starting from scratch. Come join me!
if you're new and worried about your follower numbers, don't! mastodon is more about the community and having fun with your friends. you can drop the toxic thought process where you viewed yourself as a brand on Twitter.
Use your local and federated timelines! Talk to people if something catches your eye! Don't gamify the experience here, be considerate. Think about being part of the local & federated community instead of figuring out how to go viral. Mastodon is super fun without those habits.
Politics / DSA high-quality image
@aral The "ideal solution" would probably be a software license like AGPL but which also disallows any inter-connection with instances containing proprietary code. This locks it open, but at the cost of being non-free-software (freedom zero) & annoying lots of FSF lawyers.
In the mean time, we can at least distrust any "cool new fediverse app with MIT license"
@aral Hmm, potentially a forgone conclusion, though I expect it to go like this:
1. Someone writes a very nice mastodon-like app but they license it liberally (not AGPL)
2. Someone makes a custom instance with some "cool features" which are not being upstreamed or shared
3. Lots of cool instances with cool extra features
4. Some of these instances become more commercial-centric
5. When the VCs come, already too many political connections between instance admins to make blocking possible.
@aral I feel like a lot of the user experience depends on this "mostly centralized with a fringe periphery" model. I don't have a lot of followers on my single-user-instance, so I miss out on a bunch of context when trying to view reply chains (two replies in this thread appeared as individual toots), and I can't even search hashtags reliably.
Perhaps if smaller instances were the norm, these quality-of-life issues might be more visible!
@aral @Gargron the power of the instance concept needs to be eliminated. Unless there are zero advantages to join any specific instance then large communities will congregate. Unfortunately that concept is baked into Mastodon and its forebares, we might need another iteration of the fediverse that is true p2p to order to fix the threat of centralisation.
@Gargron Another problem with #MegaInstances is that development begins to favour their form, needs, and resources. Hence we have heavyweight components like Elastic Search that mega instances can implement but which are nigh-on impossible for individual instances to support. So we now have two classes of nodes and the feature disparity will further exasperate the trend towards centralised nodes. Remember that it was superior search + “free” hosting made Gmail what it is today.
Here’s an idea: form a voluntary “Fediverse Code” that limits the size of instances to a small number. Say 100 or, at most 1,000. Any instances larger than that size are blocked.
The mega-instances we have today, like .social, voluntarily agree to cull their numbers over a period of time; aiding the migration to other instances.
The fediverse is already hugely centralised and unless we do something about it, it will be ruled by a handful of feudal lords/Mini-Jacks.
Soon, some venture capitalist will put $5 million into a startup that offers free fediverse accounts with unlimited storage, etc.
Unless every other instance instantly blocks such a service from Day 1, you can kiss your fediverse goodbye and say hello to a new Gmail. Once network effects kick in, they will make the rules.
It _can_ happen here but you have an opportunity to kill it before it does.
Today I am officially releasing Stately, a C# system for creating state machines to structure your game code.
I developed this project because I was frustrated with the lack of structure I saw behind the scenes in a lot of game code. It's flexible, facilitates readable code, and is simple enough that even novice programmers should be able to use it.
It's open-source, unit tested and licensed under GNU LGPLv3. Check it out!