silverpill

Developer of ActivityPub-based micro-blogging and content subscription platform Mitra. Working on Fediverse standards: https://codeberg.org/silverpill/feps

Public Key

npub1df0nthpgzfmvxrzj0cfypmmt45l0y770j260auqhm3l45hp3uhkqx27gmw

NIP-05 Address

silverpill@mitra-social.mostr.pub

Profile Code

nprofile1qqsx5he4ms5pyakrp3f8uyjqaa4660hj008e9d877qtacl66tsc7tmqpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qytnh6y

Publishing to

relay.mostr.pub

Author Public Key

npub1df0nthpgzfmvxrzj0cfypmmt45l0y770j260auqhm3l45hp3uhkqx27gmw

Show more details

Last Notes

2025-05-19 00:20:31

- reply

@nprofile…gm52 Sorry!
I fixed it in 4.3.1
https://codeberg.org/silverpill/mitra/releases/tag/v4.3.1

2025-05-18 21:49:36

Fediverse expands to the #Yggdrasil network.
Mitra v4.3.0 includes support for IPv6 hosts and can federate with Yggdrasil servers.
RE: https://mastodon.social/users/yggverse/statuses/114529358439259745
#nevent1q…dpze

2025-04-01 20:15:54

- reply

>the association of an as:announce activity with an as:target pointing to an as:Group actor.
I was thinking about adding target on Announce to bring FEP-1b12 and Conversation Containers closer to each other (in CC we have Add with target).
Can't Group simply be in to of Announce?

2025-03-27 17:52:31

- reply

@nprofile…3dhj I want to filter posts by language.

2025-03-26 21:04:33

What is the standard method of specifying primary language of a post in #ActivityPub?
Mastodon and Hollo add contentMap.[languageCode] to object. But Pleroma and Misskey don't.
And what if there are multiple keys in contentMap?

2025-02-20 11:44:42

- reply

@nprofile…e29w @nprofile…u78h @nprofile…v9yr I think that blocking of entire instances should be a deliberate action, not automatic, because shared blocklists can be abused. Mitra already prevents federated timeline spam by default, has mention controls, and I want to implement reply controls too. That should be enough to solve the spam problem.

2025-02-19 20:02:02

- reply

@nprofile…u78h
Thank you for writing this!
Moderation tools are slowly being added, with instance-level filters coming first. If you need a particular feature, please let me know, maybe I'll be able to add it quickly. Other comments:
- It can run on FreeBSD (there is at least one instance)
- As @nprofile…v9yr mentioned, full text search can be enabled by prefixing your search query with >.
- Could you tell me more about the "ability to hide timelines for logged-in users"? How it should work?

2025-02-14 18:08:04

Mastodon's specification for Quote Posts is finally out and... It's not bad!
It is based on FEP-e232, on top of which they add a quote control mechanism. I believe that quote controls in decentralized network don't make much sense, and currently I have no plans to implement them, but from a technical perspective, the design is quite good. Hopefully it stays that way
RE: https://mastodon.social/users/MastodonEngineering/statuses/114003104286886445
#nevent1q…p2sn

2025-02-07 16:55:26

- reply

@nprofile…u78h This particular problem was fixed in mitra version 3.16.0
But there are other issues with this client (I assume it's Mastodon official?), which I don't how to fix

2025-01-17 18:53:05

- reply

@nprofile…pc5r The feature was proposed as a Fediverse Enhancement Proposal: https://codeberg.org/fediverse/fep/src/branch/main/fep/e232/fep-e232.md.
Discussion happened on SocialHub: https://socialhub.activitypub.rocks/t/fep-e232-object-links/2722
FEP-e232 is implemented by a number of projects, but, as far as I know, Mastodon team plans to implement a different mechanism (which they don't discuss in public).

2024-12-30 19:46:41

- reply

@nprofile…f3ma You mean assets/custom.css ? This feature is still experimental so there is no example.
It is a simple CSS file. You can put whatever you want there, but the easiest way to get started is to override CSS variables. We have two sets of them, one for light mode and another one for dark mode:
https://codeberg.org/silverpill/mitra-web/src/commit/712322ae813df22119a7c0014480587ea71505c7/src/App.vue#L38-L114
Your custom.css might look like this:
:root {
/* Light theme */
--background-color: red;
}
[data-theme="dark"] {
/* Dark theme */
--background-color: green;
}

2024-12-29 20:17:02

- reply

@nprofile…w3qa @nprofile…h6f2 I'm reading about its features but I'm not seeing anything interesting. It is not clear why would anyone use it for payments instead of say monero.
And you're right, pre-mine + PoS is a red flag. Also Discord, Twitter and Telegram

2024-11-23 16:04:11

- reply

@nprofile…q3uf @nprofile…zwgs this FEP requires implementers to use FEP-8b32, which strongly recommends a specific proof type aka cryptosuite: JCS + SHA-256 + EdDSA

2024-11-23 15:00:37

"FEP-171b: Conversation Containers" finally has been published:
https://codeberg.org/fediverse/fep/src/branch/main/fep/171b/fep-171b.md
Conversation Containers are conceptually very similar to FEP-1b12: activities are sent to a conversation owner, who manages the conversation and synchronizes it between participants. Differences are mostly superficial and may disappear in the future.
#FEP #ConversationContainers #ActivityPub

2024-11-23 13:41:59

@nprofile…zwgs
>What should the fediverse do?
>Integrate decentralized / content addressed storage (ideally with an encryption layer a-la Tahoe LAFS) for posts which can survive server shutdown (like in the Golem demo I put together).
>Use mutable files within decentralized storage (Tahoe and IPFS are both examples of immutable systems which layer mutable files on top) to permit portable identity. When a user wishes to switch servers, point the inbox property at a new endpoint.
There is a much simpler solution: FEP-ef61.
Content addressing is only necessary for media.
RE: https://social.coop/users/cwebber/statuses/113527462572885698
#nevent1q…ujlp

2024-11-20 11:51:44

- reply

@nprofile…e4p9 The code expects social address in the @username@instance format, otherwise it seems to work similarly to Twitter address extractor.
The wallet should hit this API endpoint on your server when it looks up the user: /api/v1/accounts/lookup (this path should appear in nginx logs).
I pinged them a couple of days ago about this issue, but haven't heard back yet.

2024-11-19 12:13:55

- reply

@nprofile…85mj @nprofile…y0t6 This is a common failure mode of security specialists. They make perfect the enemy of the good, and start building or promoting systems that are secure but deficient in some other way: too centralized, or too difficult to use, or too difficult to implement. And ironically, those defects often make their systems less secure.

2024-09-16 15:27:31

- reply

@npub1llx…axq5 By default only user profiles are searched. In that Mitra differs from Pleroma and Mastodon who search profiles, posts and hashtags at the same time (but I think eventually I will change behavior to match other implementations).
If you want to search posts, add ">" prefix to your query

2024-09-14 19:29:58

- reply

@npub1tk4…ax9t It seems that Mastodon now fetches replies collection, I can see this in my logs too

2024-09-07 13:57:41

- reply

@npub1tk4…ax9t Yes, I saw your message. Mitra doesn't fetch replies collections automatically, only on demand. Mastodon probably doesn't fetch them either.
Maybe it's FediFetcher?

2024-09-04 01:04:02

- reply

@npub1qh0…xeda literal coolest thing ever

2024-09-04 01:00:29

- reply

@npub1wwt…ljy2 I'd use rusqlite. Sqlite is reliable, stable and it's not going anywhere. ORMs are unnecessary (IMO) and you probably won't need async in desktop application

2024-09-04 00:54:18

- reply

@npub1uh7…26ua I changed some parameters in 3.4.0, it should process outgoing activities a bit quicker now.
But a proper solution would require more work.

2024-09-03 22:25:49

- reply

@npub1uh7…26ua mitra was unprepared for high-frequency poasting

2024-09-03 17:06:35

- reply

@npub1uh7…26ua This is not caused by delivery errors. Your server is sending hundreds of messages, when normally there is 5-10 messages in the queue. What did you do before you noticed the lag?

2024-09-02 18:30:05

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

2024-08-08 13:07:34

- reply

@npub1e9k…70vv It's a FEP now: https://codeberg.org/silverpill/feps/src/branch/main/c0e0/fep-c0e0.md

2024-07-20 15:50:28

- reply

@npub1mnc…25yz FEP-ef61 makes everything domain-independent, including posts.
as:Move will only move followers, but it can work when source is offline too (FEP-7628 pull mode).

2024-06-28 07:10:09

- reply

@npub1eks…aavw
>mitra.social
>Privacy policy, no publicly accessible feed, violated our Community Guidelines or Terms of Use
Wow

2024-06-02 23:51:44

Let's talk about object ownership in #ActivityPub
I'm writing a new FEP: https://codeberg.org/silverpill/feps/src/branch/main/c7d3/fep-c7d3.md
This topic is rarely discussed, but any server that doesn't implement ownership checks as described in this document is likely vulnerable to impersonation attacks.

2024-05-25 20:51:23

can-i-use but for #SQL: https://modern-sql.com/caniuse/merge
Very cool

2024-05-08 20:49:24

Proof generation and verification algorithms in eddsa-jcs-2022 cryptosuite are changing:
https://socialhub.activitypub.rocks/t/fep-8b32-object-integrity-proofs/2725/73
#fep_8b32 #fep_ef61

2024-04-15 17:17:09

- reply

@npub1n9j…nza0 Does it actually implement ActivityPub Server to Server protocol, or only Mastodon API?

2024-04-12 23:20:51

- reply

@npub1836…8jp6 There is an option to donate to Servo development
https://servo.org

2024-04-10 21:28:36

- reply

@npub1eks…aavw There was an embarrassing bug in 2.15.0. I recommend updating straight to 2.15.1
https://mitra.social/objects/018ec04c-f239-e36d-4c6f-febc9e8d82a8
#note1awt…433k

2024-04-09 00:40:52

#Mitra v2.15.1
https://codeberg.org/silverpill/mitra/releases/tag/v2.15.1
https://codeberg.org/silverpill/mitra-web/releases/tag/v2.15.1
Fixed the lightbox

2024-04-05 16:37:43

https://matrix.org/blog/2024/04/open-source-publicly-funded-service/
>FOSS maintenance should be funded by governments on behalf of the taxpayer
Matrix people are struggling to maintain their tech and they are begging governments to take money from YOU to help them stay afloat.
Let them sink. We already have XMPP, and E2EE over AP is also coming.

2024-03-29 23:40:50

- reply

@npub1zu5…ecsa How much of this is used by mitra?

2024-03-24 22:42:51

https://help.instagram.com/914046486923176/
>When Threads blocks communication with other servers on the fediverse
>...fails to meet our Community Guidelines...
>We’ll also block a server if it doesn’t have a:
>Sufficient privacy policy; or
>Publicly available policy to restrict access to users under the age of 13; or
>Publicly accessible feed
There are two fediverses. One of them will comply with these rules, and with whatever rules come after that.

2024-03-19 10:47:08

- reply

@npub1cwk…qe8n
did:web is a standard with multiple implementations
did:plc is single implementation deployed on a single server

2024-03-19 10:30:44

- reply

@npub1cwk…qe8n No, did:plc is not good, it is just a centralized and vendor-locked version of did:web. Even if they manage to switch to a distributed architecture, fediverse developers should avoid did:plc because it is owned by a company that develops competing social network.
Good Enough solutions are did:web and did:key.
- did:web is equivalent to what we already have in Fediverse: keys are controlled by instances. But FEP-ef61 separates identity and data, so you can have data portability even though identity is still attached to a single server.
- did:key is equivalent to what Nostr does: keys are controlled by users

2024-03-18 20:37:20

Decentralized identifiers (DIDs) can be divided into 3 categories, depending on where the authority resides:
- Secret key (did:key, did:pkh).
- Server (did:web).
- Blockchain (hundreds of them).
With a #DID derived from a secret key you can truly own your identity. Unfortunately, key rotation is not supported, and if you lose your key, you lose everything. This can be partially mitigated with distributed key generation techniques that make key recovery possible if only M of N shards are available, but they are complicated.
Servers can rotate keys, but they can also suddenly disappear, and again you lose everything.
Blockchain-based systems support key rotation and don't have a single point of failure (if done right). Sometimes they are called "servers with superpowers". However, popular ones are not suitable for the job because writing to them is very expensive and their clients need powerful computing devices and a lot of storage.
Is there a way around that? Yes. Blockchains can be very lightweight and they don't actually need a cryptocurrency, miners or stakers in order to work. There is a simple consensus algorithm known as Proof of authority, and one of the Fediverse competitors, Bluesky, seems to be planning to build such system:
https://github.com/did-method-plc/did-method-plc
>We are actively hoping to replace it with or evolve it into something less centralized - likely a permissioned DID consortium.
They are afraid to say the B-word, but "permissioned consortium" is exactly what it is. Of course, their identity #blockchain doesn't have to be the only one in existence. I think in the future we might see quite a lot of "identity cooperatives" of different shapes and sizes. Perhaps even a universal client, curl for identity, can be developed.

2024-03-12 20:30:14

#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)

2024-03-12 10:44:06

- reply

@npub1mnc…25yz 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

2024-03-12 10:39:24

- reply

@npub1wc2…4sk7
Another funny Fediverse trend is cancelling projects in favor of "approved" forks
>Popular fediverse projects: Mastodon, Akkoma, Firefish.

2024-03-02 11:18:31

- reply

@npub1mnc…25yz I sent a Follow activity and received this Accept activity:
{
"@context": "https://www.w3.org/ns/activitystreams",
"actor": "https://community.nodebb.org/uid/2",
"object": {
"actor": "https://mitra.social/users/silverpill",
"type": "Follow"
},
"type": "Accept"
}
It doesn't specify what activity has been accepted (the id field is missing).
cc @npub1dxn…an9u

2024-02-12 16:26:44

This is why account migration must not depend on DNS. You can lose your domain at any time, for all kinds of reasons.
FEP-ef61 is the way.
https://akko.erincandescent.net/objects/0b812887-3946-4722-aae6-08fb64141247
#note1snv…nhpz

2024-02-11 08:55:12

- reply

@npub1pmt…d4ts Until recently the only guidance on HTTP signatures was a post in Mastodon blog from 2018 or so. This is what I relied upon to get it working back then when I started Mitra, and it appears that people still read it today.
So it's not surprising that many developers get it wrong (including myself lol).
Now we finally have a FEP draft: https://codeberg.org/fediverse/fep/pulls/257 (though there's a risk of it being abandoned).

2024-02-08 02:02:22

- reply

@npub1h73…8pv9 Thank you!
Ed25519 keys, in particular, is indeed a significant development, although in some sense it is only the first step towards the goal of data and identity portability, after almost two years of discussions and experiments.

2024-02-08 00:46:13

#Mitra v2.9.0
https://codeberg.org/silverpill/mitra/releases/tag/v2.9.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v2.9.0
Highlights:
- Generating Ed25519 keys for all accounts (in preparation for FEP-8b32 activation).
- Send notification to admin when a new user is registered.
- Legacy identity proofs are greyed out on profile page and a small button is displayed that triggers re-verification. In the near future Mitra will stop accepting legacy identity proofs (FEP-c390 identity proofs were implemented in 1.28.0 / 2023-06-26).
- Added "Federated" timeline (aka TWKN). Currently visible only to admins.

2024-01-11 18:06:16

- reply

@npub1p77…0jxq FYI, this object looks malformed: https://snac.jamesoff.net/jamesoff/p/1704978630.677698
"cc": [null],
Also one of mentions has href: null

2024-01-02 21:02:46

Fediverse tech roadmap
This is how I want our network to evolve in 2024. Some of the things listed here may have been implemented already by a small number of projects, but more work is required on standards and interoperability.
- Data portability. In my opinion, this is the most important problem. I'm in favor of FEP-ef61, which also solves identity portability and unlocks many new features.
- End-to-end encryption. MLS has become a standard, and it would be wise to adopt it. Issue 3 at fediverse-ideas provides a good overview of what we have at the moment (not much). Some variation of FEP-ae97 is likely needed to make end-to-end encryption work.
- Connectivity. Improving connectivity means fighting indiscriminate instance-level blocks, expanding to overlay networks (Tor, I2P and others), maybe also developing standards for bridges. In many ways, these tasks are linked to data portability.
- Moderation / spam resistance. Anything other than "list of instances I don't like" would be a huge improvement. Fediseer is an interesting development, but still leaves a lot to be desired. Additionally, standardization of reply controls is needed. FEP-5624 exists, but the mechanism described there has many flaws.
- Scalability. How to publish to 1M followers from a single-user instance running on cheap hardware? FEP-8b32 should make various optimizations possible (inbox forwarding, efficient reposts, etc).
- Plugins. Something like Pleroma MRF, but cross-platform (e.g. Wasm-based). Also, pluggable timeline algorithms.
- Discovery. Content discovery on small instances: relays, decentralized search.
- Developer experience. Documentation of de-facto standards (HTTP signatures, WebFinger). Simplified ActivityPub spec. Error reporting.
- Groups. We have several competing standards for groups: FEP-1b12, FEP-400e, Mastodon developers are working on their own standard. It would be nice to converge on a single standard, that also supports private groups.
- URL handlers. Again, competing standards: FediLinks, FEP-07d7 and several other proposals.
- Quoting. FEP-e232 is a proposed standard, but most fediverse applications still use non-standard properties. Mastodon developers are trying to invent something completely different.
- Synchronization of replies. Various approaches are being considered, but there's no clear winner.
- Markets. So far there's only one server implementation capable of processing payments. FEP-0837 (a protocol for federated marketplace) was designed, but lacking adoption.
- Forge federation. ForgeFed is being implemented in Forgejo, although the work is progressing very slowly.

2023-12-30 13:06:36

- reply

@npub1js9…maz4 You made it compatible with existing consumers, that's nice. But why bad example is bad is still not quite obvious to me.

2023-12-26 20:32:31

- reply

@npub108p…yev6 One man's Vegan is another man's Alt-Right
https://wedistribute.org/2023/12/authorized-fetch-circumvented/

2023-12-25 19:47:51

#Mitra v2.6.0
https://codeberg.org/silverpill/mitra/releases/tag/v2.6.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v2.6.0
This release contains many small improvements, including federation with Discourse, support for Phanpy client and automatic media cleanup after profile updates

2023-12-21 19:39:00

- reply

cc @npub1js9…maz4 @npub1vcv…9su0
I posted about this on SocialHub too but email notifications about watched topics doesn't seem to be working there, at least for me

2023-12-21 19:36:21

Important information for FEP-8b32 and FEP-c390 implementers:
https://github.com/w3c/vc-data-integrity/issues/231
It was reported that context injection is a necessary step for eddsa-jcs-2022 cryptosuite. It is necessary even if secured object is nested inside an object with @context property (as in FEP-c390).
This means FEP-c390 feature file is wrong, because I assumed that context injection is not needed. What's worse, it is not even clear how context injection must be done in this case (should we inject a string, or an array?).
In cases where top-level object is being signed, the context injection is not needed, so existing FEP-8b32 implementations are probably correct.

2023-12-19 21:56:30

- reply

@npub1xak…udwf 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"
}

2023-12-19 21:02:54

- reply

@npub1xak…udwf 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

2023-12-19 20:58:14

- reply

@npub1jl2…w5fj
gemini://git.skyjake.fi/
In markdown:
<gemini://git.skyjake.fi/>
Auto-detection is not implemented because the markdown parser we are using can't be configured to detect gemini links

2023-12-18 19:20:57

- reply

@npub1xak…udwf I'm currently in favor of IPFS URIs because IPFS folks made an effort to bring them to the Web (there's a browser extension that can open them, IIRC they even work in Brave browser out of the box).

2023-12-18 19:14:40

- reply

@npub1xak…udwf
DIDs are primarily for describing how to verify digital signatures.
For media you may use other kinds of URIs, for example urn:sha256 that you mentioned before, or IPFS URIs, or magnet URIs

2023-12-18 17:09:38

- reply

@npub1xak…udwf
>You do something similar in FEP-ef61 with did:apkey and /.well-known/apkey except for still using the did: scheme in the field values.
Yes, with the current version of FEP-ef61 you can replace DID URLs with corresponding .well-known HTTP(S) URLs.
But I want to keep pure DIDs until I gain a better understanding of this FEP by implementing it.
>Are there any Content Addressible DIDs?
Technically did:key is content addressable :)
Maybe also did:pkh
https://misterupkeep.github.io/did-ipns-spec/

2023-12-15 17:34:56

- reply

@npub1eks…aavw No, I get "too many redirects" error

2023-12-14 21:08:20

- reply

@npub108p…yev6 Yes, mitra.social had incoming requests from facebookexternalua, but at some point they stopped and I can't trigger them anymore

2023-12-14 20:47:32

- reply

@npub108p…yev6 I tried to fetch https://www.threads.net/ap/users/mosseri from my other instance public.mitra.social and received a pingback from facebookexternalua. Is it possible that they block mitra.social but not public.mitra.social? Seems unlikely. I think their federation client may simply give up after several unsuccessful federation attempts.

2023-12-14 20:02:15

- reply

@npub108p…yev6 I also see attempts to fetch instance actor in my log, but the last one was ~5 hours ago. Now when I make a signed request, threads.net doesn't react at all, even if I send a signed request as a different actor.

2023-12-08 16:28:13

- reply

@npub1utv…t50w I can see the hidden text

2023-12-06 20:54:47

FEP-e232: Object Links has been finalized
Thanks to everyone who contributed!
#fep

2023-11-18 18:14:17

I think FEP-ae97 with server-independent IDs is the best way to make identities and data portable in #ActivityPub world.
FEP-c390 + Move activity makes identity portable but not data, and requires wide adoption to provide meaningful benefits. So far there haven't been much interest from developers.
FEP-ae97 with server-independent IDs makes data portable as well, and while it is not compatible with existing software, the server can support both AP flavors at the same time, so it is not worse than FEP-c390 + Move. I also found a way to make it work with Mastodon API, that makes it a clear winner.
There is still a couple of things that need to be figured out, of course:
- What it the best way to specify a list of hosts where data is stored? I'm not entirely satisfied with ?hosts=server1.example,server2.example solution.
- How to encrypt data? It's harder to maintain confidentiality of private messages when they are stored on multiple servers, therefore they should be encrypted.

2023-11-16 18:56:41

My actor passes all tests at https://verify.funfedi.dev
https://verify.funfedi.dev/?actor_uri=https%3A%2F%2Fmitra.social%2Fusers%2Fsilverpill

2023-10-31 19:25:23

- reply

@npub1m29…khl9 Right, senile bureaucrats should be kept as far as possible from anything intelligent.
But is it a real thing? Even if it is real, it probably won't last for long.

2023-10-23 17:12:46

- reply

@npub1hf5…pc2h It is quite slow compared to clearnet, but not unbearable. I downloaded a 400 MB music album, it took approximately 1 hour with 4-6 seeds
Feels like early 2000s and eMule

2023-10-23 16:37:23

qBittorrent v4.6.0 includes #I2P support
...and it just works! All I had to do is launch i2pd service, enable "I2P (experimental)" in qBittorrent's preferences and download a torrent file from http://tracker2.postman.i2p

2023-10-01 19:16:18

- reply

@npub199l…az5c 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?

2023-10-01 06:37:27

- reply

@npub14aa…72lh 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?

2023-09-30 20:15:54

- reply

@npub14aa…72lh ActivityPub can use a transport protocol other than HTTPS (if you read the spec in a certain way). I wrote this document which describes self-authenticating activities:
https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md
I think it's a good stating point for p2p-ActivityPub.

2023-09-28 18:25:50

#Mitra v1.36.1
https://codeberg.org/silverpill/mitra/releases/tag/v1.36.1
https://codeberg.org/silverpill/mitra-web/releases/tag/v1.36.1
A small bugfix release. Probably the last one before 2.0.0

2023-09-19 14:25:01

#Mitra 1.36.0
https://codeberg.org/silverpill/mitra/releases/tag/v1.36.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v1.36.0
Highlights:
- Subscription payments can be sent from one instance to another (previously, navigating to recipient's instance was the only way to make a payment). See FEDERATION.md and FEP-0837 for details.
- Local timeline made accessible to guests (if enabled in config).

2023-09-15 14:22:59

- reply

@npub1k2u…gk9j Yes, but only at the backend. Public timeline is not supported by the mitra-web client yet.

2023-09-15 14:21:22

- reply

@npub1nl9…fh6t If actor is moved (copied) from A to B, how other servers should verify that A and B are controlled by the same person?

2023-09-11 12:50:50

- reply

@npub199l…az5c Test reply. Thanks for fixing outbox, by the way

2023-09-11 11:21:07

#Mitra v1.35.0
https://codeberg.org/silverpill/mitra/releases/tag/v1.35.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v1.35.0

2023-09-10 14:30:52

- reply

@npub120z…33r2
>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
https://www.w3.org/TR/activitystreams-vocabulary/#dfn-place

2023-09-08 12:17:59

FEP-67ff: FEDERATION.md
https://codeberg.org/fediverse/fep/src/branch/main/fep/67ff/fep-67ff.md
Yet another Fediverse Enhancement Proposal. FEDERATION.md file is used by some projects to document the federation protocol.
Here's the one I wrote for #Mitra: https://codeberg.org/silverpill/mitra/src/branch/main/FEDERATION.md

2023-09-05 20:43:38

- reply

@npub1nl9…fh6t @npub1npf…3lrs Where can I find the spec for nomadic identity?
I started writing a FEP on the migration / nomadic identity subject and it will be incomplete without a reference to Nomad: https://codeberg.org/silverpill/feps/src/branch/main/7628/fep-7628.md

2023-09-05 09:26:20

- reply

@npub1r9j…4h54 @npub1nl9…fh6t @npub1npf…3lrs 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).

2023-09-05 06:44:02

- reply

@npub1npf…3lrs 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

2023-08-31 19:06:11

#Mitra v1.34.0
https://codeberg.org/silverpill/mitra/releases/tag/v1.34.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v1.34.0
Implemented "locked" accounts and follow request management.

2023-08-30 20:11:01

@npub1yry…c8tp
How do you think it's going to be used?
There's an open issue about making local timeline publicly accessible: https://codeberg.org/silverpill/mitra-web/issues/2

2023-08-29 22:14:17

- reply

@npub1e3d…vz9r 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

2023-08-25 23:38:14

- reply

@npub1xak…udwf @npub1jwj…egwq Let's ping the developer who's working on AP intergration @npub1mfe…2zxh

2023-08-25 20:03:44

- reply

@npub1xak…udwf @npub1jwj…egwq
Does it work for you?
I'm getting 500 internal error in response to Follow

2023-08-18 22:16:50

- reply

@npub1wwt…ljy2 @npub1pnp…52zw 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.

2023-08-18 16:19:01

https://mastodon.social/users/torproject/statuses/110906828593942566
@npub1a3r…9clu announced they will participate in Gitcoin funding round and everyone immediately started attacking them, saying it's a scam, and telling them that they don't need the money (lol).
Well, Gitcoin is basically a crowdfunding platform. It's definitely not a scam, and I know many FOSS projects that used it. Also, Gitcoin is actually interesting because they use an innovative donation matching mechanism called Quadratic Funding (see https://www.wtfisqf.com).
There's nothing wrong with Tor Project using this platform to raise more money. Trying to prevent them from doing so is absolutely insane, and this is what brainwashing by "web3 is going just great" does to you. This account is slandering good projects while constantly promoting actual scams which no one would ever heard of otherwise.
#note1w09…7fre

2023-08-18 03:13:20

#Mitra v1.33.0
https://codeberg.org/silverpill/mitra/releases/tag/v1.33.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v1.33.0
Highlights:
- Previewing remote subscription options. Mitra now shows a page with subscription price even if the user is on another instance (but you still need to navigate to another server to make a payment).
- Further improvements to message delivery queue.

2023-08-17 18:16:57

- reply

@npub1970…we4s The Read activity is defined in ActivityStreams vocabulary: https://www.w3.org/TR/activitystreams-vocabulary/#dfn-read. I don't know if anyone uses it but a similar View activity is used by PeerTube: https://docs.joinpeertube.org/api/activitypub#view

2023-08-16 13:05:36

- reply

@npub1k2u…gk9j :mitra:

2023-08-15 22:01:13

- reply

@npub1vqz…kttk Yeah, good idea. Thank you for your feedback!

2023-08-15 17:00:24

- reply

@npub1vqz…kttk How the documentation could be improved? CONFIG_PATH is mentioned in "Installation - Building from source" section of the README. Should it be documented elsewhere?
>SO\_PASSCRED
Interesting, didn't know about this trick. I will add postgres://mitra@%2Fvar%2Frun%2Fpostgresql/mitra along with other common variants to the config example.