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_at_mitra.social@mostr.pub

Profile Code

nprofile1qqsx5he4ms5pyakrp3f8uyjqaa4660hj008e9d877qtacl66tsc7tmqprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmdqy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqk0d9f

Publishing to

relay.noswhere.com

relay.mostr.pub

Author Public Key

npub1df0nthpgzfmvxrzj0cfypmmt45l0y770j260auqhm3l45hp3uhkqx27gmw

Show more details

Last Notes

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-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-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-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-05-25 20:51:23

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

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-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-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-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-08 16:28:13

- reply

@npub1utv…t50w I can see the hidden text

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 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-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 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.

2023-08-15 14:05:23

- reply

@npub1vqz…kttk
>manual follower approval
Mitra only shows a lock icon if remote account requires approval. Local follow requests and approvals have not been implemented yet, but I'll keep in mind that this feature is needed.
>I tried casually to use pleroma-fe with a mitra-backend but that didn't work for me.
If there is any specific incompatibility, I could try to fix that.
Also, bloat-fe mostly works, if you're into that kind of thing.
>I had to shit up my VPS with node so I can rebuild the frontend. Prebuilt assets would be nice.
You can extract static files from a deb package (I provide debs for every mitra-backend release: https://codeberg.org/silverpill/mitra/releases/tag/v1.32.0).
I think I could add these static files to mitra-web releases as well.

2023-08-14 18:47:32

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.

2023-08-10 16:59:51

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

2023-08-10 02:08:46

- reply

@npub1jl2…w5fj Mitra will be able to do profile backfilling. Actually this feature has already been implemented and I'm using it frequently - but it is only available to instance admins (as a CLI command).

2023-08-09 01:46:51

- reply

@npub12xf…9ps4 @npub1ar0…62dm Tier 0 is "worst of the worst" but they just add random instances to it. My single user instance is also there even though I never communicated with them.
Why indieweb is using it?

2023-08-09 01:18:01

https://milksad.info/
>We discovered a cryptographic weakness in the widely utilized Libbitcoin Explorer (bx) cryptocurrency wallet tool while following up on mysterious wallet thefts.
>Bad actors have discovered this flaw and are actively exploiting it to steal funds from affected wallets on multiple blockchains.
Seems to be pretty serious.
https://mastodon.social/users/lrvick/statuses/110855860330518325
#note1qn3…z448

2023-08-08 20:54:34

- reply

@npub1fxm…n42c So, what's the practical difference between these two models?
This is not the first time I hear about this distinction, but it always sounds like a talk about implementation details.

2023-08-08 02:23:12

- reply

@npub108p…yev6 Because fiatjaf couldn't endure people saying mean things about Bitcoin in the network and felt the urge to create an isolated safe space? I think you're absolutely right.
By the way, why did you cut off the part where they accepted Rebased into the list? https://codeberg.org/fediverse/delightful-fediverse-apps/pulls/39#issuecomment-993410

2023-08-08 00:25:47

- reply

@npub1km2…gk9z The official Mastodon for Android app? I don't know, but it might work.
Mitra API is similar to Mastodon API.

2023-08-07 20:34:42

- reply

@npub1ar0…62dm And they are launching it as ERC-20 token, which means there's no privacy whatsoever.
Scammers

2023-08-07 16:27:26

- reply

@npub17dl…dj38 Lemmy accepts Follow, Like and Create activities, so follows, likes and replies from Mastodon should work.
Among activities Lemmy sends, Mastodon should be able to process group announcements and replies.
>And how do I post to Lemmy from mastodon with decent format?(if possible)
The first line gets transformed into a title.

2023-08-07 15:52:39

- reply

@npub108p…yev6 Nice.

2023-08-07 15:37:53

- reply

@npub1ahk…rlfs Yes, unfortunately you are right. We still have a lot of work to do.

2023-08-07 02:37:24

https://github.com/cloudflare/wildebeest
Cloudflare didn't make it
>This project has been archived and is no longer actively maintained or supported

2023-08-06 01:37:13

- reply

@npub1pmt…d4ts The recommended type is still Proposal, but it is not a hard requirement anymore. Flohmarkt is using Note and I think that makes sense. FEP-0837 shouldn't prohibit this.
That being said, other projects might choose to use attachments. Mitra uses Link attachments that contain references to proposals. For example, my actor object (https://mitra.social/users/silverpill) has this attachment:
{
"href": "https://mitra.social/users/silverpill/proposals/monero:418015bb9ae982a1975da7d79277c270",
"name": "MoneroSubscription",
"rel": [
"payment",
"https://w3id.org/valueflows/Proposal"
],
"type": "Link"
}
The href attribute points to FEP--0837 proposal (or a subscription page, depending on the media type in Accept header).

2023-08-05 22:55:49

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").

2023-08-05 19:23:10

- reply

@npub12ty…vnqc @npub10l3…ht5s
Please consider MLS, end-to-end encryption protocol standardized by IETF: https://blog.phnx.im/rfc-9420-mls/
Matrix and some other messengers are going to adopt it, so there's a possibility that we can interoperate with them in the future.

2023-07-24 19:10:10

- reply

@npub1tus…g5wt I'm designing a protocol for federated marketplaces: https://codeberg.org/silverpill/feps/src/branch/main/0837/fep-0837.md (not a new protocol really, just an extension of ActivityPub).
This will allow different marketplaces to interoperate

2023-04-07 00:39:04

#Mitra v1.20.0
https://codeberg.org/silverpill/mitra/releases/tag/v1.20.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v1.20.0
Highlights:
- Moving followers from Mastodon/Pleroma.
- New page for managing aliases. It displays both "unverified" aliases (they are necessary for migration from Mastodon/Pleroma), and cryptographically verified ones (based on identity proofs).
- Basic spam filtering.
- Dark mode is not experimental feature anymore.

2023-03-30 16:18:23

#Mitra v1.19.0
https://codeberg.org/silverpill/mitra/releases/tag/v1.19.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v1.19.0
Dark mode is available now. It can be enabled in Settings, where the toggle button is hidden in "Experiments" section.
https://mitra.social/media/d73ad9b94b63a5d92b735fec17ebdf114c73096aa6d4f042d75893ffacf6f002.png

2023-03-21 20:21:53

#Mitra v1.18.0
https://codeberg.org/silverpill/mitra/releases/tag/v1.18.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v1.18.0
No new features this time, just various small improvements and fixes.

2023-03-08 02:27:56

#Mitra v1.16.0
https://codeberg.org/silverpill/mitra/releases/tag/v1.16.0
https://codeberg.org/silverpill/mitra-web/releases/tag/v1.16.0
Highlights:
- Allowed to add notes to generated invite codes.
- Allowed to use different proxy for requests to .onion domains. Clearnet instances now can federate with Tor instances.
- Use/@username routes for profiles (e.g. https://mitra.social/@silverpill).
- Render custom emojis in display names.