multihash-serialise VS Mastodon

When I click on https://synapsemedia.io/ I get redirected to a link like https://ipfs.io/ipns/synapsemedia.io (to use ipfs.io instead of my local node)

You may already be aware that the Interplanetary File System or IPFS is a distributed storage network where computers from all over the world form nodes to share data.

In case of you don't trust them, it gets harder. Especially if you need to have it hosted without any trace to yourself. I'd probably pay a service to store my data on ipfs. You can pay with crypto. But I'm this case there's the question, how will you be able to access it. My thought would be to have a [tails][tails] USB with the necessary software.

https://ipfs.io is the only acceptable file host

I never click GET button, don't even know what it does tbh XD Those four buttons are for choosing which IPFS gateway you want to use. By default I use ipfs.io, if ipfs.io is down then I click the Cloudflare one. General rule is that you pick one gateway if it does not work then another one and so on.

- The gateway (e.g., ipfs.io, cloudflare, w3eth.io, w3link.io) may implement a censorship rule based on local regulations

https://ipfs.io/ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco/wiki/

New to IPFS, both ipfs.io and Cloudflare IPFS are blocked in my region, but I can connect to IPFS using the IPFS desktop app, is there a way to download books at a relatively not too slow speed from anna's archive's ipfs mirror?

Web 3.0 is a third-generation website with decentralized server storage from layer two blockchains like Ethereum, polygon, etc. Unstoppable domains are the first web3 domain platform where you find different domain names. This platform uses a crypto name system called CNS. Unstoppable domains used IPFS (interplanetary File System), the best file protocol that allows computers to store and serve files as part of a giant P2P network. shreyanshjain.crypto is my domain name minted on the polygon network.

Oh, TIL about https://mastodon.social/ (https://joinmastodon.org/)

Looks like what you describe, doesn't it?

> Social networking that's not for sale.

Interestingly there is some discussion for Mastodon with people asking the limit to be smaller, which raises the question as to the purpose of alt text, and how to properly handle larger text lengths in screen reader programs.

https://github.com/mastodon/mastodon/issues/12268

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

Mastodon DMs have absolutely no privacy: https://github.com/mastodon/mastodon/issues/18079

For a decentralized protocol doing things right is much more important than doing things fast, it is very difficult (and in a lot of cases impossible) to break backwards compatibility.

Postmortem on what happened here: https://news.ycombinator.com/edit?id=39305884

The v1 API of Mastodon limits the size of the tree that it will expand for users who are not logged into the server: https://github.com/mastodon/mastodon/blob/main/app/controllers/api/v1/statuses_controller.rb . I am guessing that this or some similar limit applies to threads being returned to unauthenticated users of the web UI. It just arbitrarily stops expanding the replies at some point, including the main thread from the OP.

If a thread is truncated, users expect it to expand automatically and autoscroll when you hit the bottom. In my desktop browser, that does not occur, and there is no indication that there is more to see. This is the situation of the web interface as of Mastodon version 4.2.5.

The issue is very sensitive to observer conditions. If you are logged into the server, the behavior is different. If you use a Mastodon app instead of the web, the behavior might be different. As the tree expands, the cutoffs become different. If you look at the thread on a different Mastodon server, the tree is different because every server has its own view of the Fediverse.

HN needs a best practice for linking to Mastodon threads in a way that provides a consistent experience to HN readers. The average Mastodon server would be crushed by hundreds of HN readers grabbing the entirety of a huge thread all at once, so this might involve some thread-unroll-and-cache service. I tried https://mastoreader.io/ but it did not solve the problem.

Alternately, we push changes into the Mastodon web UI to warn users when they need to click to see more and assume that people will get used to the navigation.

Suggestions?

Fixed in Mastodon v4.2.5 https://github.com/mastodon/mastodon/releases/tag/v4.2.5

>You can defeat the Affero clause by putting the software behind a proxy, for example

Could someone elaborate on this? This is NOT my understanding of the license, and it seems absurd considering e.g. Mastodon is AGPL but the standard install requires a reverse proxy[1]. If using a proxy defeats Affero, why would the Mastodon team do this? Are they stupid?

[1] https://github.com/mastodon/mastodon/blob/main/dist/nginx.co...

Mastodon is free and open-source. Go ahead and add the flag:

https://github.com/mastodon/mastodon/blob/main/CONTRIBUTING....