"Đavelorp quản lý hộ inbox chung với 10-12 người gặp vấn đề: email lộn xcrotook, mất/xóa. L فكانت thử phần mềm nhưng không đáp ứng. Mình cần giải pháp theo dõi di chuyển email & quy trген. Bạn có gợi ý nào? #SharedInbox #EmailManagement #TeamSupport #SoftwareSolution #InboxChiaSẻ #QuảnLýEmail #HỗTrợTrượt #GiảiPhongBSoft"
https://www.reddit.com/r/SaaS/comments/1ocdb5g/software_to_manage_shared_inbox_with_multiple/
The ActivityPub specification does not have an example of the "sharedInbox" field in use.
Although it does say "An optional endpoint..." — I suspect a lot of people won't know (with confidence) that it can go under the "endpoints" field. For example:
"endpoints": {
"sharedInbox": "https://social.example/inbox"
},
Especially if the person is still trying to understand ActivityPub, and isn't aware of the "endpoints" field yet.
#ActivityPub #DeSo #FediDev #FediDevs #Fediverse #SharedInbox
Yes, there exist a #SharedInbox to reduce traffic. So if you would have 1000 followers on #server B and you are on server A, it is just one #message for one #toot between A and B.
Usually #federation starts with the first #follower. So if you are on server A and noone follows you on instance B, your toots will not be federated.
But... it would be possible to search on B for the full URL to fetch an unknown toot from another instance.
Can someone explain to me what happens when I publish a toot on #Mastodon?
If I had 1000 followers on server B, would there be a network communication for each follower or does Mastodon use something like a #sharedInbox? Or is there something like a #relay?
If I had no followers on server B, would my toot still be forwarded to server B? Could my toot then be found on server B e.g. via a hashtag search?
I got around to reading the ActivityPub spec. and it's pretty nice! I'm wondering how implementations decide when to create a shared inbox. Seems like a potentially interesting algorithm.
Reddit Tech VN Bot
@reiver ⊼ (Charles) 
Nordnick 
Torsten 
glyn
dansup234