You are not logged in. Log in. Or Sign up.

NOTE: Federation is disabled on this instance!

You can test federation between the following instances:
Vervis @ dev.angeley.es
Home PAGE TITLE HERE
{
    "summary": "Suggestion: Remote Sharers",
    "mediaType": "text/html",
    "@context": [
        "https://www.w3.org/ns/activitystreams",
        "https://forgefed.peers.community/ns",
        "https://angeley.es/as2-ext"
    ],
    "context": "https://dev.angeley.es/s/fr33domlover/p/vervis",
    "history": "https://dev.angeley.es/s/jazzyeagle/t/oQJlv/events",
    "published": "2020-06-09T13:03:11.347126Z",
    "dependants": "https://dev.angeley.es/s/jazzyeagle/t/oQJlv/rdeps",
    "dependencies": "https://dev.angeley.es/s/jazzyeagle/t/oQJlv/deps",
    "content": "<p>One of the things I’ve had issues with in terms of Federation is that I have to have completely separate accounts for every type of instance I want to upload. I have one for Mastodon, I’d need a separate one for PeerTube to upload videos, etc. The idea is this: When someone registers to be a sharer, they can register using a pre-existing federated account, which would be authenticated by requiring me to log in to the federated account via OAuth2. Then my Sharer account on Vervis would be set up to point inbox/outbox and other related links in the Sharer record to my federated account instead of to a local Sharer account, meaning the federated account will manage my inboxes and whatnot for me, but I can still create projects and repositories on Vervis.</p>\n<p>I’m not sure how well that would work, but I think it’d be a cool feature if we could make it work.</p>",
    "replies": "https://dev.angeley.es/s/jazzyeagle/t/oQJlv/d",
    "participants": "https://dev.angeley.es/s/jazzyeagle/t/oQJlv/followers",
    "isResolved": false,
    "team": "https://dev.angeley.es/s/jazzyeagle/t/oQJlv/team",
    "source": {
        "mediaType": "text/markdown; variant=Pandoc",
        "content": "One of the things I've had issues with in terms of Federation is that I have to have completely separate accounts for every type of instance I want to upload.  I have one for Mastodon, I'd need a separate one for PeerTube to upload videos, etc.  The idea is this:  When someone registers to be a sharer, they can register using a pre-existing federated account, which would be authenticated by requiring me to log in to the federated account via OAuth2.  Then my Sharer account on Vervis would be set up to point inbox/outbox and other related links in the Sharer record  to my federated account instead of to a local Sharer account, meaning the federated account will manage my inboxes and whatnot for me, but I can still create projects and repositories on Vervis.\n\nI'm not sure how well that would work, but I think it'd be a cool feature if we could make it work."
    },
    "id": "https://dev.angeley.es/s/jazzyeagle/t/oQJlv",
    "type": "Ticket",
    "attributedTo": "https://dev.angeley.es/s/jazzyeagle"
}
[See HTML]