I've seen a LOT of horrible tech ideas in my time. But the Microsoft announcement for a Windows feature (apparently enabled by default) to take and store screenshots every few seconds of everything you do on your PC has to be one of the most high privacy risk concepts I've ever seen. Even stored locally on the PC, it's a recipe for domestic abuse, government abuses, and a long list of other nightmares. Microsoft has jumped the shark BIG TIME.
OK #Linux community, listen up.
MS have done it again and people are looking for a way out.
DON'T TREAT NEWBIES LIKE SHIT.
DON'T ATTACK PEOPLE FOR ASKING QUESTIONS.
DON'T ATTACK PEOPLE FOR HAVING PROBLEMS.
DON'T TELL PEOPLE TO "GOOGLE IT" WHEN THEY COULDN'T POSSIBLY KNOW WHAT TO SEARCH FOR, OR HOW TO INTERPRET THE RESULTS THEY'D FIND.
DON'T BE A DICK.
Hey y'all! I'm looking for a pixel artist to help out on my game!
"Enigma Heart" is a retro-styled side-scrolling action RPG. There are no palette restrictions, although I would like to keep the visual style in roughly the SNES era. Tile size is 16x16; most characters are 1 tile x 2 tiles (16x32).
Some of the graphics have already been done by me and another artist, so a style similar to ours/ability to match it, is a must. Screenshots of the game (as it currently stands) are attached to this post.
Needed are graphics of the player character, some NPCs, monsters, and dungeon and town backdrops/tilesets.
Please reply to this post, or if you're more comfortable with a private mention, that's fine too.
Boosts are greatly appreciated!
We've adopted saying "for morale" rather than "as a treat".
e.g.,
Turns out we do a lot of things for morale.
(@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
fedi meta, why I'm wary of allow-list federation
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