@mikedev I can spot several differences between this document and the latest revision of FEP-ef61:
- FEP-ef61 now uses gateways property, not gateway. I changed the property name because its value is an ordered list (and we already have replies and orderedItems, so a plural doesn't feel inappropriate).
- Canonical object ID has no path component. FEP-ef61 says that path is REQUIRED (according to RFC 3986, the path can be "empty", so I should probably change it to "path MUST NOT be empty").
- The value of proof.verificationMethod is a "compatible" ID, but according to FEP-ef61, "The value of verificationMethod property of the proof MUST match the authority component of the ap:// URL". In other words, it must be a DID.
Of course, all of that is up to discussion, and the spec can be changed if necessary.
>The sticky spots I see right now are abstracting a more portable url for profile-photo, cover-photo
We can use content-addressing. See Discussion / Media section.
>and ed25519 publickey
I assume you're referring to the need for it to be a server-owned key? Per FEP-521a we can add multiple keys to assertionMethod array. Each nomadic clone can use its own key for signing HTTP requests, only the identity key (the "authority" part of 'ap' URL) must be shared.
>You should be able to import the resulting record into any FEP-ef61 compliant server running on any fediverse platform and have one identity to rule them all.
In my implementation exported objects and the ones sent via S2S protocol will probably look the same, because in the future I will perform proof generation on the client side. This means the server will not be able to change published objects, its role will be merely of an indexer.
I think a lot of this "criticizing Biden is helping Trump/Putin" stems from a way of thinking that places all of the responsibility and blame for how things go politically on the people with no power at all.
In this way of thinking Biden isn't responsible or accountable to us at all, but WE are responsible for supporting him.
This is twisted.
TZAG all.
In case you are doomscrolling:
An Italian court has rejected charges that Mediterranean refugee rescue NGOs were encouraging "illegal migration".
Automobile factory workers in Tennessee have voted overwhelmingly to create a union.
And I am out to weed and prune, now that the early morning shift of rock doves, stock doves, sparrows, rooks, jackdaws, starlings, blackbirds, magpies, dunnocks, robins, and who knows who else have been fed on too-old leftovers, peanuts, and seeds.
What is the “observable fediverse”?
Simply put, “observable fediverse” is the content that you can see. It was based on the astronomy phrase “observable universe” where it means the part of the universe we, Earthlings, can see.
It is very similar in the #Fediverse. What your account can see is just your account's own “observable fediverse”. This means that, anything you see is actually a very small part of the fediverse. Just as how the universe we can see is just a very small part of the entire universe.
Yes, keyword is “very small part”.
If there are 1M active fediverse users, you are more likely only consuming content from 100 fediverse accounts. The rest, you either ignore or they just don't reach you at all.
In other words, your experience in the fediverse, and what topics you frequently see, were all based on what you created it to be. It also doesn't represent the fediverse network at all.
Examples:
* Account A mainly sees music content; coupled with art and their local news from Country Z.
* Account B sees a lot of news content from Country Y.
* Account C is toxic because the content this account often receives are debates, toxic political discussions, and anti-this and anti-that.
The users of those accounts are the ones who created what they can see and interact with, not the fediverse. And it doesn't represent the kind of content in the fediverse.
In conclusion: What content you see was built by you, and only applies to that account.
Give it a try. Create multiple accounts in different instances and follow different people and subjects. Once you understand this, it gets easier to see the content you want.
I realized what it is about the eclipse image set that makes it so challenging to find and use #astrophotography tools to align them all.
In many cases with astro images, the goal is stacking, i.e., aligning a feature of interest across multiple images where that feature is positioned arbitrarily. In effect, you're "solving" for a *single, static* variable, and assuming anything that doesn't correlate with it is noise and can be safely eliminated.
/1
Ryan,
How refreshing!
Another bridging mechanism to extend the reach and interoperability with other Fediverse protocols in the #DeSoc space is most welcome, and from the limited analysis I've been able to perform so far this is a novel approach to what some point in the future will find other Fediverse platforms incorporating in their network stacks.
So far, we've got seamless nostr interoperability to add to the other fine protocols such as Diaspora, ZOT, Nomad, OStatus, ActivityPub, and others in the mix. You might also wish to take a look at the repo for Minds to see how they've made seamless integration between the ActivityPub and nostr portions of the #Fediverse as well, and oh, pay no mind to the infantile and disparaging remarks that some small minded folks in this thread have exhibited - they are free to *defederate themselves from the Fediverse at any time.
We've been following withe some enthusiasm your project in the Fediverse-City community and it would be a pleasure to have you participate there. Your insight into the open and public aspects of Fediverse traffic in the #DeSoc world is a testament to the innovation and evolution that is possible in obviating the proprietary, privacy disrespecting, deprecated monolothic silo networks that have sowed so much acrimony and subjugation over the very people whom they seek to quantify as their business products.
You're performing a great service here, feel free to block any miscreants in this thread who don't understand the definition of public.
Also, might I suggest that instead of offering a `#nobridge keyword index, you think about offering a solution as a FEP here?:
https://codeberg.org/fediverse/fep/
There are a lot of Fediverse platform developers I'm sure that you'll find welcoming, encouraging, and willing to offer assistance in formulating solutions to silence the adolescent juvenile mindsets that have been berating you in this thread for your selfless commitment to the well being of us all.
In the future, the Fediverse that we perceive and interact within will become its own heterogeneous superset of networking protocols to facilitate effortless communications between individual parties regardless of which portions of the Fediverse and their associated protocols implemented. Just like #OStatus has been largely supplanted by ActivityPub, and #ZOT has been superseded by #Nomad, the ActivityPub portion of the Fediverse will also eventually be deprecated and replaced by other stacks that will emerge from the ether of creativity. In the meantime, we'll be bridging between the various protocol stacks, and Bridgy-fed is one of those tools that serves to make that a reality :)
Thank you again, for your selfless contribution to #DeSoc and the Fediverse. it's a fantastic achievement that will serve to benefit many in both the #ATP and #ActivityPub portions of the Fediverse!
#tallship #bridgy #FOSS #Fediverse #DeSoc #innovation
⛵️
.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.