If you are interested in running for Board or Council, please add a wiki page about your candidacy to one or both of the following sections until November 5th, 2023, 00:00 UTC. (Board application does not require XSF membership.)
Over the past few years we’ve often sympathised with Sisyphus in the Greek legend. Sisyphus had to push a boulder up a hill for eternity only for it to go rolling back down again as soon as he neared the summit. Not wishing to tempt the notoriously vengeful Greek gods, but we’re increasingly certain that this time we’ve...
We’ve often sympathised with Sisyphus in the Greek legend. Sisyphus had to push a boulder up a hill for eternity only for it to go rolling back down again as soon as he neared the summit.
Not wishing to tempt the notoriously vengeful Greek gods, but we’re increasingly certain that this time we’ve finally cracked it, and we’re sitting pretty on the plateau. Why the confidence?
Meta claims that Threads will eventually become federated, meaning that it, too, will allow you to take your followers and port them elsewhere, and that it will possibly become interoperable with Mastodon at some point. There are reasons to be skeptical of this actually happening, which have been explained much better by other people but largely have to do with the fact that Facebook likes to monetize its users and strives for social media monopolization. I believe it would be very good for the internet if Threads were to earnestly and actually federate itself, but, for now, I will just point out that Threads is still not interoperable with the continent of Europe for reasons of “it’s illegal there because of Facebook’s privacy practices” and thus I’m not holding my breath.
If you are at all worried about how complicated Mastodon is or can be, you can ignore this part, join Mastodon.Social, and never think about the rest of this article. Anyways, portability is good and important because, let’s say that hypothetically Mastodon.Social were to be taken over by some maniac billionaire. I could choose to take my account and port it somewhere else, and bring my followers with me. What a concept!" https://www.404media.co/mastodon-is-the-good-one/
It’s great to have got to the stage that client side at least we can check into the forum, ask for logs when something isn’t working and fix it on the fly. Case in point, the problem with missing chunks when downloading large files. In that case it was a matter of batching chunks when downloading. In fact it’s been a good...
💡 Understand the closed-source and centralized nature of Twitter and its impact on freedom
💡 Explore the consequences of a restrictive API and the loss of ownership
💡 Learn about issues in biometrics, data mining, and surveillance
💡 Discover the limitations of controlling your social graph and the invasive nature of ads
💡 Delve into the anti-free speech and anti-net neutrality practices
Here we’re looking to further test out some client fixes to various timeouts and other issues we’ve applied in the course of the prior testnet. We’ll also be keeping an eye out for “lost nodes” (nodes that start but do not appear to join the network successfully). We’ve removed code to this end, that seems to have...
With the HeapNet2 testnet having just left the launchpad, it’s time to review the previous one, MemDebugNet. MemDebugNet served us extremely well, before inevitably spiralling into Weimar Republic territory due to the highest StoreCost in a close group being the one that gets paid. We are changing how that works by discarding...
We’ve had two testnets on the go in the last week, aiming to clarify issues in replication and at the client, as well as investigating the mem increases we’ve seen across nodes.
So far, while we’re still seeing client issues, we’ve been able to clarify what’s going on there and so fixes to failed CashNote reads, and other upload issues, are in the works.
We’ve had two testnets on the go in the last week, aiming to clarify issues in replication and at the client, as well as investigating the mem increases we’ve seen across nodes. So far, while we’re still seeing client issues, we’ve been able to clarify what’s going on there and so fixes to failed CashNote reads, and...
We’ve another testnet hopeful to address some replication flows (or at least give us more insight into any issue) and to allow for sampling of node memory for debugging any memory leaks that may still persist (or at least identify if it is just the cost of connections thus far). We’ve other improvements to logging around the...
Did you know that #tilvids is completely funded by our awesome community? No privacy-invading ads, just a community of creators and viewers building something together. 🙌
If you'd like to help support the costs for running our video community, consider donating to our Patreon! 💙
Discussion of the #gossipsub feature of Safe Network. Could #ActivityPub be implemented as a peer-to-peer protocol on to of gossip? Allowing federation to extended to include p2p applications?...
This week we’ve been looking at the results of the testnet and working on fixes for bugs. The first thing to note is that, to make debugging easier, the testnet was deliberately unforgiving, with a chunk having to be replicated to all eight close group nodes to be considered valid. That said, it did unearth some strangeness...
Yet another testnet that anyone can try out (on Windows, Mac and LInux). Test aims: firstly we want to be sure if removing the attempted kad-caching has helped with data-put reliability (as described in the dev update. This is our main point to dig in on for this testnet, hopefully gaining a bit more clarity via… The new...
Finally got around to migrating all my non-trivial git repositories from MS/GH to #Codeberg - just before the 2FA-MS/GH-probably-will-require-your-telephone-number deadline. :) I'm keeping my account there since some communication [1] with #TyrannyOfConvenience people can still be useful.
@Gargron 's branch of Mastodon still has issue 22572 of #GiveUpGitHub migration unsolved [2].
Another day another #testnet! After the last IntolerantNodeNet, we’re looking more concretely at the client. One part of the last testnet was aiming to see how clients performed with the concurrency and batch-size arguments, but a bug in StoreCost retrieval largely scuppered that effort. Here we want to: Confirm our fix is in...
Safe Network Update 26 October, 2023 (safenetforum.org)
Over the past few years we’ve often sympathised with Sisyphus in the Greek legend. Sisyphus had to push a boulder up a hill for eternity only for it to go rolling back down again as soon as he neared the summit. Not wishing to tempt the notoriously vengeful Greek gods, but we’re increasingly certain that this time we’ve...
Safe Network Update 19 October, 2023 (safenetforum.org)
It’s great to have got to the stage that client side at least we can check into the forum, ask for logs when something isn’t working and fix it on the fly. Case in point, the problem with missing chunks when downloading large files. In that case it was a matter of batching chunks when downloading. In fact it’s been a good...
Woop, another testnet: HeapNet2!!! [12/10/23] (safenetforum.org)
Here we’re looking to further test out some client fixes to various timeouts and other issues we’ve applied in the course of the prior testnet. We’ll also be keeping an eye out for “lost nodes” (nodes that start but do not appear to join the network successfully). We’ve removed code to this end, that seems to have...
Safe Network Update 12 October, 2023 (safenetforum.org)
With the HeapNet2 testnet having just left the launchpad, it’s time to review the previous one, MemDebugNet. MemDebugNet served us extremely well, before inevitably spiralling into Weimar Republic territory due to the highest StoreCost in a close group being the one that gets paid. We are changing how that works by discarding...
Safe Network Weekly Update 5 October, 2023 (safenetforum.org)
We’ve had two testnets on the go in the last week, aiming to clarify issues in replication and at the client, as well as investigating the mem increases we’ve seen across nodes. So far, while we’re still seeing client issues, we’ve been able to clarify what’s going on there and so fixes to failed CashNote reads, and...
Woop another testnet!! MemDebugNet [4/10/23] (safenetforum.org)
We’ve another testnet hopeful to address some replication flows (or at least give us more insight into any issue) and to allow for sampling of node memory for debugging any memory leaks that may still persist (or at least identify if it is just the cost of connections thus far). We’ve other improvements to logging around the...
Gossipsub, what dat? (safenetforum.org)
Discussion of the #gossipsub feature of Safe Network. Could #ActivityPub be implemented as a peer-to-peer protocol on to of gossip? Allowing federation to extended to include p2p applications?...
Safe Network Update 28 September, 2023 (safenetforum.org)
This week we’ve been looking at the results of the testnet and working on fixes for bugs. The first thing to note is that, to make debugging easier, the testnet was deliberately unforgiving, with a chunk having to be replicated to all eight close group nodes to be considered valid. That said, it did unearth some strangeness...
Safe Network #Testnet DataDebugNet [ 28/09/23] (safenetforum.org)
Yet another testnet that anyone can try out (on Windows, Mac and LInux). Test aims: firstly we want to be sure if removing the attempted kad-caching has helped with data-put reliability (as described in the dev update. This is our main point to dig in on for this testnet, hopefully gaining a bit more clarity via… The new...
Safe Network Testnet: ClientImprovementNet [22/09/23] (safenetforum.org)
Another day another #testnet! After the last IntolerantNodeNet, we’re looking more concretely at the client. One part of the last testnet was aiming to see how clients performed with the concurrency and batch-size arguments, but a bug in StoreCost retrieval largely scuppered that effort. Here we want to: Confirm our fix is in...