How many domain names your government needs to block in order to censor an entire network?
Bluesky: 1 domain name
Nostr: 680 domain names, but blocking 10 most popular relays and hosted clients would probably be enough to kill it
Fediverse: more than 20000 domain names
#Fediverse #Censorship
@dcf0b831 mention links should have u-url class (and maybe mention too), and they should be wrapped into <span class="h-card"> element.
hashtags should have rel=tag attribute
@26318dfd clearnet and darknet hosts can interact without a bridge. The clearnet host should be configured to send requests to .onion/.i2p hosts via Tor/I2P proxy, and darknet hosts usually don't need to do anything special, they just connect via exit nodes.
For example my instance can talk to both onion and i2p hosts.
#ActivityPub proxy by @tedu: https://flak.tedunangst.com/post/idkfa
Looks very interesting. This service rewrites activities, so in theory it can work as a bridge between disconnected parts of Fediverse, for example between two defederated servers, or between server-centered Fediverse and client-centered Fediverse, or between #Tor instances and clearnet instances.
@Anark Karabey I think the button could simply insert [[url]] into a new post.
Do you want it to notify the author about a quote (by default there's no notification, quote is just a link to another post).
Also note that quotes are not supported by Mastodon and Pleroma (although Pleroma may implement them soon). Users of these services will see a regular link without preview.
@81cbff92 Pleroma supports direct Note too (although it displays direct Notes and ChatMessages differently in the UI). I don't know about Misskey, but it is likely that their non-standard field is not important for interop.
@tedu As a first step, we can start accepting Ed25519 keys in addition to RSA keys. As far as I know, publicKey field can't be an array, and even if it can, many projects will fail to process an array there.
There's another proposal that describes a way out this situation: https://codeberg.org/fediverse/fep/src/branch/main/fep/521a/fep-521a.md
With a new property that can contain any kind of public key, implementations can start adding Ed25519 keys to actors. Once a sufficient portion of Fediverse supports EdDSA, projects can start using it for outgoing requests and activities
@297ef8d1 Re-following is performed during account migration, it is triggered by Move activity (the process is described in FEP-7628). I guess if object and target of Move activity point to the same actor, it can be interpreted as "re-follow me" signal. However, if your followers table is lost, how would you know where to send this activity?
@tedu FEP-8b32 recommends EdDSA integrity proofs as a replacement for outdated and non-standard RSA linked data signatures. This is a good way to introduce EdDSA into Fediverse, but so far there was not much interest from developers.
@e8df75ff
>aligning incentives better than most projects
This aligns incentives in one particular domain: marketing. The project quickly turns into ponzi scheme because nobody is interested in actual tech, all you get is paid shills everywhere
@af7acbe6 By the way, MaidSafe, is it that company from early blockchain days? I thought the project was long dead, but recently it started to appear again in the media. What going on there? Some kind of reboot?
@NotMtth If you have a Codeberg account you can leave a comment there saying that you have the same problem. Same with Husky. Issues of this kind are difficult to debug from the server side.
@0ed7afc8@djsumdog Vue (especially 3.x) tries to be close to vanilla JS, I'm actually enjoying using it.
Never understood why people use something like React where markup, styles and code are mixed together. Every React project I've seen looks like giant pile of spaghetti.
@Anark Karabey@NotMtth Tor-only instances can only federate with clearnet instances connected to Tor network (like yours). When server receives an ActivityPub message, it must verify the signature, but if signer's public key is served by an onion service and the server is not connected to Tor, verification fails.
@Anark Karabey@NotMtth He wants a Tor-only instance that can federate with the whole Fediverse, but it's not possible. Not possible without a bridge
No word from him since we discussed that.
@639ed14f I think machine-readable data can be added to markdown as YAML front matter. Or capabilities can be exposed via NodeInfo, some servers already do that.
Just updated FEP-0837 draft ("Federated Markets"). The proposal objects are now allowed to have type other than Proposal, e.g. Note. This means servers can publish proposals that are compatible with Mastodon (which only accepts a limited number of types as "posts").
@376dfe7d I'm not particularly fond of IPFS either, but what are other options?
I think IPFS URIs can be useful even without IPFS node, as a more widespread alternative to urn:sha256
@376dfe7d If reference to media file is did:apkey URL, it can be translated similarly to object IDs.
Instead of encoding content hash directly in the URL, one can specify it in the object that represents media attachment:
{
"type": "Image",
"mediaType": "image/jpeg",
"href": "did:apkey:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK/media/1.jpg?hosts=server1.example,server2.example",
"digestHex": "deadbeef"
}
@NotMtth I use only web interface, but I've tried Husky once and it (mostly) worked for me.
Could you describe the issue in more detail? Does it show any error message, or just a login screen?
The deb package attached to 1.36.1 release contained a mitra binary with higher libc/libssl requirements, and it caused breakage on older systems.
I removed the 1.36.1 package and built a new one with statically linked binaries:
https://codeberg.org/silverpill/mitra/releases/tag/v1.36.2
Notes by silverpill | export