Posts by mikedev@fediversity.site
(DIR) Post #AimNmIXWRUWhUlmJgO by mikedev@fediversity.site
2024-06-10T00:18:25Z
0 likes, 0 repeats
Just successfully followed a nomadic ActivityPub identity from Mastodon and was able to communicate both directions. That work is in a different branch and not included in the current release, but is also moving along quite nicely.
(DIR) Post #AinTk8PfupBIONQ49Y by mikedev@fediversity.site
2024-06-10T19:21:40Z
0 likes, 0 repeats
From my point of view, it is an object that is owned by somebody and can be attributed to somebody and should be signed if you wish to verify the attribution. If you don't wish to sign collections I can respect that -- as long as I encounter no attribution issues related to the collection itself. I would however complain loudly if you arbitrarily decided that I am forbidden to sign them.
(DIR) Post #Aj8HYNknPhyfI8NkdE by mikedev@fediversity.site
2024-06-20T22:18:45Z
1 likes, 4 repeats
Please boost if your immediate circle contains fediverse developers outside of Mastodon. I'm trying to determine the scope of support for the Mastodon's platform "Move Account" activity across the fediverse. We intend to use this in the relatively near future to convert all of the streams repository's ActivityPub facing accounts to nomadic digital identities - without losing all of our ActivityPub friends in the process.I'm certain we'll find a number of fediverse projects that don't support this activity and will require manual re-friending. If you have knowledge of any platforms which don't - please reply with the platform name so that this procedure is well documented and we don't have a lot of surprises and missing friends. Thanks.
(DIR) Post #AjIjI2KDJ0LV3wSIGu by mikedev@fediversity.site
2024-06-25T22:52:34Z
0 likes, 0 repeats
My work on #Nomadic Identity over ActivityPub was stalled for a bit. Nomadic identity itself isn't that hard. It's the migration to upgrade folks from non-nomadic accounts that is the challenge. Finally found a way to move forward again. The actor record itself now has three different "views", which are selected by options. The traditional ActivityPub view, the nomadic ActivityPub view, and the exportable view - which can be imported into any other nomadic ActivityPub application or project. So to perform the Move operation and get all your followers onto the new identity, we'll just switch views - depending on what URL you access. Still a few loose ends to work out, but it's coming along.
(DIR) Post #AjL9NdiZQzEI4SUBvs by mikedev@fediversity.site
2024-06-26T22:43:14Z
0 likes, 0 repeats
No point in moving your identity if your content server shuts down unexpectedly. I'm actually working on nomadic content over ActivityPub right this moment. Centralising it destroys everything I've done with nomadic identity over the last dozen years. We have clonable identities (identity and content) right now with live synchronisation. If your server cert expires or goes offline right this second, go to your clone and nothing has changed. You have all your content, friends, and settings. Everything. I'm not giving this up and neither should you. Content-addressable mechanisms don't work because the url changes if you edit the object. Every project has completely different URL paths and object-type mappings.I'm currently convinced the only way to solve this is with a mapping table, so that /item/something on my system can be found at /object/something on your system (or whatever). We also have 30-40 different object types that most other projects haven't even considered. This is the only way to make them portable. Just store the object in the mapping table instead of the local path mapping for that object. Done. The portable url could just be $apgateway/$did/$resource-id. If my software supports that kind of object I'll redirect to where we store that kind of object. If it doesn't, I'll just return the portable object. Cheers.
(DIR) Post #AjM3BTEMC99LVG7zI8 by mikedev@fediversity.site
2024-06-27T11:28:11Z
0 likes, 0 repeats
Evan had a Farmville clone for ActivityPub's predecessor pump.io. We've dabbled in some other server-side apps, like putting chess games into your stream - but the killer is letting strangers execute javascript in your stream. We ran some experimental stuff in sandboxed iframes, but finally decided it was a bad look for the free web and said yeah,nah.
(DIR) Post #AjMZvrab9v0iu8hG2S by mikedev@fediversity.site
2024-06-27T19:32:57Z
1 likes, 0 repeats
An intermediate win would be arbitrary forms (beyond polls). We support form rendering in our AP objects today, but still waiting for motivated developers to provide a backend layer to provide storage and processing and make it useful. I'm far too busy with other stuff to give this idea the love it deserves. For apps, I'll just mention what we did with Hubzilla as food for thought. Hubzilla is an access controlled CMS with access-controlled social components. One of the CMS objects you can create is an 'app' which is nothing more than a potentially access-controlled link with an icon that you can install in your personal channel. It "executes" any web link. Where it gets interesting is that these apps can be accessed-controlled CMS pages created by other Hubzilla members. Or any link you want to provide. And we can share the app in our social stream and let other folks save them and install them on their own channel. I used to use a 3rd party weather app all the time. One of the best examples of this created by members is an online store of goods by visual and audio artists and the link can be restricted to authenticated fans. Oh, and the apps themselves can be paid.Supporting these objects over ActivityPub isn't that difficult really. It comes down to a rendering of an attached object. We could even do remote storage for your own app collections and let you access them with your fedi-id. Then your personal app manager is nothing more than an app that you can install and share. So as above, so below. I think people here lost interest as the fediverse moved to primitive text-based microblogs and away from integrated community tools and ecommerce. Maybe the pendulum will swing back the other way someday.
(DIR) Post #AjUgeea2WiRyZvr73Y by mikedev@fediversity.site
2024-06-21T21:01:33Z
0 likes, 0 repeats
FWIW that was received here and and ap urls are allow-listed generally, but it's too late now to see what the HTML-Purifier did with the original link. It has its own allow-list which hasn't been modified. Will need to create a unit test for that as I suspect it might have been filtered or otherwise mangled in transit. Then there are a few places in the codebase where we might actually rewrite/resolve those, but based on your experience it appears there's no hurry to do so.
(DIR) Post #AjhPJ0tbhkK5FiaBWK by mikedev@fediversity.site
2024-07-07T21:00:35Z
1 likes, 1 repeats
@Streams Announcing version 24.7.8 from the streams repository. "The best fediverse server you never heard of."In this release: nomadic identity over ActivityPubnomadic content over all supported protocolsjson-ld webpage metadata ("fediverse:creator" can rot in hell - we use and promote open standards here). ...and much morehttps://codeberg.org/streams/streams
(DIR) Post #Ak5IoACo6XMbqZksuO by mikedev@fediversity.site
2024-07-19T05:37:37Z
0 likes, 0 repeats
An age-old problem.Transfer protocols:HTTPActivityPubE/SMTP information formatting specifications:HTMLActivityStreamsRFC822
(DIR) Post #AkBpkmeJgzn7M6NVQG by mikedev@fediversity.site
2024-07-22T08:24:32Z
0 likes, 0 repeats
No need to over-think it. #⚠️
(DIR) Post #AkCV36y6ys9hhwUkue by mikedev@fediversity.site
2024-07-22T20:11:25Z
0 likes, 0 repeats
Welcome to the fediverse. It isn't ruled by Twitter or Mastodon. We use hashtags to tag unsafe content here. It's part of the pre-existing culture you're trying to destroy in the quest to dominate and control. We also use Unicode and HTML. Length limits are optional. And we support using the 'summary' field as a summary.Hashtags are content labels. What else did you think they were? They work across platforms and protocols and do not require an FEP. This solution wasn't chosen by geeks - it was chosen by the people of the fediverse long ago to tag their content. The original fediverse/federation projects built filters to let you choose what tags you wanted to collapse or block - if any. In this way the receiver is in control of what they don't wish to see. Not platforms, not protocols, not corporate owners. The sender just provides advice through the use of content tags (specifically hashtags). The platform (i.e. the fediverse or a specific project or product) is (or at least should be) neutral. It's a system that works.
(DIR) Post #AkRSsqgnMnEbmklzYe by mikedev@fediversity.site
2024-07-29T12:20:23Z
0 likes, 0 repeats
I think we're "mostly" interoperating. At the moment, only brand new streams accounts have nomadic ActivityPub accounts. Pre-existing accounts have traditional ids, however some content will be using gateway resolvers before they fully transition. I've got a couple of fully nomadic accounts that I've been testing with. I've seen a couple of http-signature issues that I'm currently trying to resolve - where the legacy url was signed but the gateway url was verified. But those are edge cases; most stuff is working. I can see your stuff just fine.
(DIR) Post #AkUgZ9x01dCqZ2jnzU by mikedev@fediversity.site
2024-07-31T06:37:06Z
1 likes, 0 repeats
The quote-posts situation is depressing. We finally got consensus that FEP-e232 was the right way to move forward and a number of us moved forward. Then Eugen came along and said - "no -- Mastodon has to be able to forbid people from quote posting our content." As mentioned in an earlier comment, that's un-enforceable in a decentralised network. And if it's un-enforceable, it's a bullshit feature. Same as they did with 'canSearch'. Sorry folks, but if the data is on my server, how the heck are you going to stop me from searching my database? What - I can't search my own database -- because you said so? It's a bullshit feature. I'm sticking with FEP-e232. And I've got an alternate federated search proposal based on open standards and real permissions. I can only prevent you from searching my database. As for comment controls, last I looked Pixelfed was using some kind of undocumented rights structure using OCAP that Ariadne cooked up for Pleroma. I suspect Mastodon will go forward with canReply and a simple list of actors/collections. I can live with that - even though we can do a few more things they haven't thought of yet. I'm moving some of our Nomad permission stuff to ActivityPub and that will be personalised. You send a signed request to the permissions endpoint and it will return a list of what you can and can't do, like upload photos and moderate my channel. Reply controls sort of need to go with the Activity, because we can change it on a per-post basis. But my permissions endpoint will tell you whether you can comment at all - by default. There's a lot of nuance and a lot of conflicting implementations. And you're going to have legacy players like WordPress and Threads that can't really change their infrastructure and won't be able to implement one FEP or another with a complete re-design. Best thing I can suggest is to lay them all out on a table and try and find some common ground and build from there.
(DIR) Post #AlUtX0gcqKqaSQtqz2 by mikedev@fediversity.site
2024-08-29T22:13:25Z
1 likes, 0 repeats
That's a promise not available on the Fediverse ...until now.Premium follower subscriptions in the fedi first appeared in Redmatrix in 2014. I think they're still available in Hubzilla.
(DIR) Post #Aln8CqEH0dtEOIl3Q0 by mikedev@fediversity.site
2024-09-08T05:39:36Z
0 likes, 0 repeats
Last year, I moved conversations into Collections identified by the context element, and we only accepted Add/Remove activities for collections from Collection->attributedTo. All submissions were made to them and only to them. We previously sent replies only to the thread originator - a concept for restricted access conversations I came up with about the same time the Diaspora folks did. We kept it for a number of years even though Mastodon didn't support it, but moving conversation threads into a simple collection management operation not only makes sense, it bloody works brilliantly and co-exists with microblogging. It also co-exists with FEP-7888.
(DIR) Post #Am1USqQkwkhyqy4Veq by mikedev@fediversity.site
2024-09-06T21:26:18Z
0 likes, 0 repeats
Tried to get a constrained conversation model into ActivityPub for over a decade. Finally settled on this:https://fediversity.site/help/develop/en/ContainersI didn't create an FEP specifically for this because it's just a minor tweak to a couple of existing FEPs. This provides a mechanism to easily implement reply controls, moderation, groups, private groups, conversation completion, relayed deliveries, circles and much more. And it's all generic ActivityPub and co-exists with microblog software. I added a little indicator in the UI so you can see at a glance if the conversation you're participating in is safe or not.
(DIR) Post #Am1rMvsg4EqCxvHWO8 by mikedev@fediversity.site
2024-09-14T23:21:26Z
1 likes, 0 repeats
Hmmm. What is this "Windows button"?
(DIR) Post #AmCumGsPa0nbvJUT2m by mikedev@fediversity.site
2024-09-15T10:25:34Z
0 likes, 0 repeats
I don't mind.
(DIR) Post #AmCxAYOWIfnp72DPto by mikedev@fediversity.site
2024-09-20T21:48:31Z
0 likes, 0 repeats
I can foresee a lot of confusion over the mingling of '@context', 'context', and 'Context'. Do you have a recommended LD namespace for the latter, and should it be a type with multiple properties (['OrderedCollection', 'Context'])? It wasn't obvious from the document. Otherwise that looks good.