Life is Tetris @tetrislife@qoto.org

I should be clear that I admire and respect people who set up Fediverse servers and let strangers join. That is an amazingly generous and thoughtful thing to do. People who take on this and other tasks for running Fediverse servers deserve our gratitude and support.

We are an in-between project. #deltachat is in-between traditional messengers and email apps and #p2p paradigms, #chatmail is in between the massive email server network and #webxdc is in-between e-mail, @xmpp and the web ecosystem (but outlaws central platforms) ... Our approach is rhizomatic, i.e. based on, and changes with, various collaborations and joining contributors. We don't have stable funding and need to regularly apply for public funds ... And are surrounded by VC funded projects

@evan
i think a case can be made that torrents have the best track record and are super stable in terms of where the development is. its very straightforward how to seed data , and you can do all of this on your servers so its completely invisible to the user.

downside of torrents is they are immutable . eg cannot change ,, you could chunk your torrent creations possibly or you could use one of

my friend @mauve has an example of how to use mutable web torrents :
https://github.com/RangerMauve/mutable-webtorrent

I hate how "do you have something to hide" is a question asked only to users of technology, but not to tech companies.

Thinking about the Mozilla situation, I get the impression that a related problem is that the web world is full of wrong incentives.

E.g. people react to a bad web-site's behavior as "this browser sucks". But since a browser is nothing more than a VM, they could just as well say "this computer sucks".

Maybe good browsers should start displaying "web site benchmarks": for example show in something like a "status bar" the number of HTTP requests performed so far for the web page, the number of hosts contacted, the number of bytes downloaded, the number of JS method calls performed, the number of JS field accesses, etc...

Measurements that try to be browser-agnostic so they reflect the efficiency of the web-page itself.

[ and by "show" I mean "by default", rather than as some kind of developer-only option. So it needs to be sufficiently unobtrusive. ]

Maybe we could then come up with some quantitative estimation of the "useful information content" (UIC) displayed and then show an efficiency result as a ratio of those measurements against the UIC?

Or we could plug average estimated energy cost of each one of those things measured and display the Joules or carbon cost of the web-page?

Another dimension would be to try and collect information about the features used so as to be able to display "displays correctly only with a Firefox more recent than year 20XX".

@evan

IPFS no, it's a poor match, particularly for browsers or PWAs.

Mastadon's current implementation is so horrendous it feels like it was specifically designed to enrich cloud providers.

The way PeerTube uses s3 storage, Torrents, Node2Node redundancy, and P2P in the browser solves the issue for video way more elegantly and effectively.

There are much options the Mastodon corner of the fediverse could choose to fix their issues, #jortage is a better starting point for one.

#mastoAdmin

https://jortage.com/ takes the "duplicate every image across every fedi server" model and deduplicates as possible at the media storage level

self-hosting an instance and outsourcing media storage has been for me a nice balance

i just upped my contribution a bit

thought you should all know about #jortage

It'd be nice if this expensive "fiber optic" internet I pay for had basic features like IPv6 🙃

@ploum @oneploumshow Personally I'll just consider putting stuff on #IPFS & #BitTorrent instead as that's way more efficient and doesn't require centralized platforms at all...

Just like the ...

It's still only mid-morning, but "ruin-time library" might already have won Typo of the Day.

Maybe the secret why the #deltachat project with "just" a dozen active contributors succeeds in delivering cross-platform apps, instigating the #chatmail server network and spearheading the #webxdc app paradigm, lies in asking the right questions:

- Is it really needed?

- Can we not do it?

- Is there a simpler way that requires less changes?

- What is the interesting next impl step that is already interesting itself for users, without requiring first completing a big refactoring project?

@praveen
> For now I'm focusing on XMPP as I think replacing WhatsApp is more important right now

Fair. 2 questions;

1) Are you familiar with the @snikket_im project to build a modern, easy-to-use chat experience using existing XMPP software? (Full disclose: I've done little bits of paid contracting for it)

2) Why XMPP, and not Matrix, Delta.Chat (E2EE chat over email protocols), or Sup messenger (E2EE chat over ActivityPub)? Just curious.

https://wedistribute.org/2023/08/sup-by-pixelfed-is-coming/

#chat #XMPP

So a data researcher at #huggingface decided to scrape a million bluesky posts as a dataset.

Then proudly announced what they did.

Then apologised and took it down. 😐

This is what someone brought up in a culture that hasn't been brought up to consider consent does. The kind of culture that declaims it's easier to ask for forgiveness after than permission.

I say a culture, but I shouldn't sugar coat it. This is what being brought up under white supremacy does.

https://social.coop/@graue/113551951939078430

@jalefkowit I'd reply with "Something was fixed." and forget about it until they tell you something detailed.

(I wouldn't really, obviously, but I'd want to.)