Metal Mutton 🤖🐏 @SteelWool@computerfairi.es

We've adopted saying "for morale" rather than "as a treat".

e.g.,

• Having a nap for morale.
• Eating ice cream for morale.
• Spending time relaxing with my wife for morale.

Turns out we do a lot of things for morale.

#AsATreat #ForMorale #MentalHealth

And we thought dealing with a bug that lost photos on iOS was bad, turns out the opposite might be worse:

(@2DArray · May 9, 2018)

::_::cls()srand()
for i=0,99 do
x=rnd(128)
y=(rnd(128)+t()*(40+rnd(10)))%128
pset(x,y,rnd(3)+5)
end
for i=0,20 do
for j=0,2 do
for k=0,.08,.004 do
a=i/15+k-t()/4
y=137-i*8-j
line(64+cos(a)*4,y,64+cos(a)*40,y+sin(a)*10,5+j)
end
end
end
flip()goto _

https://pico-8-edu.com/?c=AHB4YQD3ALmnBPcWwc3Hv8H6fPIGVz-A4Vm2cvoLhOvnH3bNKWcFVRymDxGmrjjoorv67iW6Ba8e9AxJdlFy1kZmrqIKgoNskb7C1AO06cROX9jmsLa_LInTsSFF4ZUFRRG3vIFbzPoI1jitGfJAMeOZwaW928YWJtrbRAaqUnYgG7muKufyZmBlNFuZ2bouX5jdHMx2xhZCqQG3Z2ltri373jk7XTfVjciPeXR2pJxcGHiDjc1idhk=&g=w-w-w-w1HQHw-w2Xw-w3Xw-w2HQH
#Pico8 #TweetCart

Recent events have spurred some great discussion of fediverse safety and the ways that we can improve it. I'm thrilled to see the growing interest in this problem, but there's one specific angle that concerns me. Specifically, the push for allow-list federation.

First, some background information. Federation between instances is usually controlled by restricting which remote instances (identified by domain name) can send or receive messages from the local instance. In the majority of fedi servers, this is implemented with a "deny list" - a list of instance domains that should be blocked. When using a deny list, all unlisted domains can communicate by default.

This is in contrast with an "allow list", which specifies the domains that should not be blocked. When using an allow list, all unlisted domains are blocked and can not communicate. Deny-list federation is open except for specific routes, and allow-list federation is closed except for specific routes. There are other approaches, but these are by far the most common.

Now, moving on to my actual point. I've recently seen some discussion of using allow-list federation as means to improve user safety. This idea, while very well-intended, is unfortunately flawed and could easily cause more harm than it prevents.

This idea suggests that by limiting federation to known, approved domains, then it becomes easier to block sources of abuse, hate, and illegal content. This is actually quite effective, and some instances are already using allow lists to great effect. They experience minimal contact with dangerous instances, and those that slip through are easy to identify and block. It's a great strategy for specific communities. Unfortunately, however, this approach cannot scale.

Allow-list federation works well for a minority of instances, but only because the majority do not use it. This is due to the network effect. Just as a centralized social network can collapse if there are too few connections between users, a federated social network can collapse if there are too few connections between nodes (instances).

With open or deny-list federation, all nodes are connected to all others. This forms a very strong network - so strong that small and even single-user nodes are possible. The open federation ensures that there are always sufficient connections to keep the network useful.

The same is not true of allow-list federation. In this mode, the network nodes are only connected to a limited subset of others. As the percentage of allow-list nodes increases, the number of connections decreases exponentially. The resulting network is weak and unstable enough to collapse under pressure. A bigger problem, however, is not the network weakness but rather the loss of small instances.

In my experience, it's rare to see a federation allow-list with more than 1,000 entries. Fediverse index websites currently show around 25,000 active instances, which means that most allow-list instances are connected with only 4% of others. We can assume that the 4% is biased towards medium-to-large instances because of their increased visibility. After all, an instance cannot allow-list another node until they've encountered it through a mutual. Larger instances have more mutuals, and thus a greater chance to be discovered.

Over time, this creates an imbalance where larger instances benefit from a richer and broader network than smaller nodes, who have limited reach and reduced federation. Any new instance must somehow maintain a user base while faced with network isolation. This becomes a significant barrier to entry for the fediverse.

This barrier effect is bad enough, but there's another angle to consider. Fedi is large enough to have a constant churn of small instances starting up and shutting down. Currently, more instances are forming than closing, which leads to positive growth in the number of nodes - a good thing for network health. But if it was harder to start a new instance? That ratio would drop or even reverse, causing the network to shrink instead of grow. Reduced network size increases the network effect, which expands the inequality, which strengthens the barrier, which decreases the growth, which reduces the network size. A classic feedback loop.

This process would be devastating for fedi. The cycle would continue until there's no new instances at all, by which point we'd have lost the rich ecosystem of tiny communities that make fedi unique. Large instances can never provide a truly safe space, and often foster a community much like Twitter - problems included. The small, diverse instances are what make this network special. If we lose that, then we lose the fediverse.

I can't bear to see that happen.

#Fedi #FediVerse #FediMeta #Federation

Gave 🔴 an 👁️
#screenshotsaturday #pico8 #indiegames #gamedev

i love seeing critters remember gifts given to them and returning the favor! mutuality is really so beautiful i love being alive i love my relationships with all the different critters and plants in my life i want to take them all so much further

chromium based more like chromium cringed

firefox will now track your searches by default and you'd have no way of knowing they're doing that unless you look for this random blog post on their website: https://blog.mozilla.org/en/products/firefox/firefox-search-update/

it does look like you can turn it off at least.

can't tell me this isn't skilled labor 🥑💨

Secret Panel HERE 😰 https://tapas.io/episode/3181095

Sending this energy out to those who need it #today

The system is working exactly as intended...

Gente que no ponéis texto alternativo en las fotos:
Por favor, recordad que las personas ciegas o con visión reducida no sé enteran de lo que estáis publicando. Pero si ponéis una descripción de la imagen, el lector de pantalla lee esa descripción y entoces sí.
Me resulta súpertriste pasarme por «local» y ver la mayoría de las fotos sin alt :_(

(Por si no pones el alt porque no sabes cómo ni dónde: al cargar la foto, si le das al lapicerito que sale en la parte de abajo, te lleva a la pantalla para introducirlo. La manera de describir la imagen es como si se lo contaras a alguien por teléfono)

If you follow me there's a good chance you're using/will use some of my pixel fonts: in that case, can I ask you a favor?

Can you please go and rate them on Itch? Thanks!

https://somepx.itch.io/

#fonts #pixelart #gamedev

It's frustrating how many organisations are still using Twitter to announce important info to the public. There is no way for most people to see this info! Most people aren't on Twitter, and Twitter now requires a sign-on just to view profiles.

If you want to announce stuff to the public, the only way to make sure it's visible to everyone is to use your own website, your own blog, your own social media server. Anyone with an internet connection can see them.

#GrowYourOwn #SelfHosting #Twitter

laziness isnt real and calling someone lazy is probably ableism