With the latest release of #Mitra, the media proxy feature has stabilized and is ready to use.
When enabled, it significantly reduces storage requirements because the remote media is not saved to disk. It also guarantees that you don't accidentally store anything illegal.
However, since it is a proxy, the media is not loaded directly from remote hosts, so they won't learn your IP address and browser fingerprint, only the time when you're online.
Media proxy can be enabled for all hosts or only for selected ones (because it is a part of the federation filter system):
mitra add-filter-rule proxy-media '*'
mitra add-filter-rule proxy-media pawoo.net
RE: https://mitra.social/objects/0198be5c-dfef-8dca-3ac4-b370a79d372f
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqm299scpk0n8gqnjkmftjzr56mqa4zqlxkwha7p43c7y6zusw5desrk85mj I think you're right. This is certainly true for Mastodon and several other popular projects where developers not only provide means for running huge instances with hundreds of thousands of users, but run such instances themselves. In that environment mod/admin drama is guaranteed.
But not all developers are like that. Some are working on making small instances affordable.
nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqy3p3f3xld8ex2y6a5v6xqlgzwkua24ff7erqlx6vhyync6jfztqscdd3ay It does, but this collection doesn't have an id property (anonymous).
can-i-use but for #SQL: https://modern-sql.com/caniuse/merge
Very cool
#Mitra v2.13.0
https://codeberg.org/silverpill/mitra/releases/tag/v2.13.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v2.13.0
- Notifications about emoji reactions.
- Public posts can be exported in FEP-ef61 format (exported objects are not very useful at the moment, but it's a first step towards data portability)
nostr:npub1mnctsv04f02w3cj7yyvfhny4lynk6h33t6kp9wxl2u4ztzpg7cfqh425yz mention links should have u-url class (and maybe mention too), and they should be wrapped into element.
hashtags should have rel=tag attribute
nostr:npub1wc2kznjw6kldwzz8eedr9pf208waa8ww3fjsqk0nz4rdv8q663qswt4sk7
Another funny Fediverse trend is cancelling projects in favor of "approved" forks
>Popular fediverse projects: Mastodon, Akkoma, Firefish.
nostr:npub1xaklulvyjhcvljrd4lgn7cswj5sa9ewphvn0zswq0gfcadn2qv0qlwudwf 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"
}
nostr:npub1xaklulvyjhcvljrd4lgn7cswj5sa9ewphvn0zswq0gfcadn2qv0qlwudwf 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
nostr:npub1nl98j7g9kxkdh5f3u0cxltk8dl0gwt77kxxmk5wtlmstufjrkkqsk0fh6t If actor is moved (copied) from A to B, how other servers should verify that A and B are controlled by the same person?
nostr:npub199l035f22rvyg59yc4stva9cgsnvmpld58ge9me2h09wun67nnvsl8az5c Test reply. Thanks for fixing outbox, by the way
nostr:npub120zh308gs69j3vwgvvrzgglv58vsk3q0vef43uajyu0lc3mtldsq2p33r2
>We're also working on an Activity extension spec for geotagging, so other projects can use this too\!
You don't need to. The location property and Place type are part of ActivityStreams:
https://www.w3.org/TR/activitystreams-vocabulary/#dfn-location
nostr:npub1r9jrhg4d249sn7z7pyunpsa9zcdr7rjtg90x3w3e78a7jrp7wadsvw4h54 nostr:npub1nl98j7g9kxkdh5f3u0cxltk8dl0gwt77kxxmk5wtlmstufjrkkqsk0fh6t nostr:npub1npfq3e25jyyvsdfppkasx2hmgwr4kazxzrsrlp3t7y252vyhexhsnk3lrs As far as I know, there's no documentation for streams' implementation of nomadic identity. I think I managed to grasp the overall idea from various conversations but not enough to build an interoperable software.
The reason I prefer DIDs over multi-home model is that there's no need to register accounts on other servers in advance (although I could misunderstand something about Nomad).
nostr:npub1npfq3e25jyyvsdfppkasx2hmgwr4kazxzrsrlp3t7y252vyhexhsnk3lrs When the ActivityPub spec was written the standard for decentralized identity didn't exist. But now Decentralized Identifiers (DIDs) is a W3C standard, so we can tackle this problem.
Take a look at this proposal, for example: https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md
nostr:npub1e3dt2stusesttu8g8en5fn8zycnzlk0qwgm2ckzxl864fdje5a5slgvz9r I think it was inspired by other protocols like Secure Scuttlebutt, and so far I haven't seen much innovation there. Yes, it has advantages over Pleroma, because your Nostr identity is not attached to any particular server and therefore server admins have less power over your communications.
It's entirely possible to do the same in Fediverse though. Recently I published a protocol extension proposal that describes how you can build a client that controls account's private key and uses servers as relays: https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md
nostr:npub1xaklulvyjhcvljrd4lgn7cswj5sa9ewphvn0zswq0gfcadn2qv0qlwudwf nostr:npub1jwjj6hku083y23zrhavz9hf5sps3ve2yfuh0pat6feumf702lczs69egwq Let's ping the developer who's working on AP intergration nostr:npub1mferaw5j5j737s2k5duuf67lxwn5kx876f7tr579t0q7xpd0udvqk32zxh
nostr:npub1wwtte6l7xjhylhsut3dt7d3yg2qqekvq50wjldkyvmue5u305edqkkljy2 nostr:npub1pnpez7cn4h04pxg07dmmklzyz7u7fm0w2ddrw220qh785rq3m42ql452zw If you're interested in hacks and scams, I recommend https://rekt.news instead.
They are doing good investigative journalism without trying to discredit the entire industry.
FEP-ae97: Client-side activity signing
https://codeberg.org/silverpill/feps/src/branch/main/ae97/fep-ae97.md
I've been experimenting with client-side signing for quite some time and decided to write a document describing a complete solution. It builds on my past proposals (FEP-8b32 and FEP-c390), and if widely implemented, will allow users to send activities from anywhere, without tying them to a particular server.
I'm still not sure if client-side signing makes sense for Mitra, but some other projects like Vocata might support this.
#Mitra v1.32.0
https://codeberg.org/silverpill/mitra/releases/tag/v1.32.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v1.32.0
Highlights:
- Improved delivery performance (concurrent requests, tracking broken/unreachable inboxes).
- Admin account can be automatically displayed at "About" page (off by default).