Searching txt.sour.is

Twts matching #follows.
Sort by: Newest, Oldest, Most Relevant
stigatle
yarn.stigatle.no
 (3y ago)
↳ In-reply-to » Often people run a node somewhere, then connect to it with the remote node feature from other machines. Or use a light wallet. Cpu use will go down when block chain is synced. Also just a tip - check the prune blockchain feature to save a lot of space.

@shreyan@twtxt.net first time I’ve seen someone mention gnu taler. Been following it since it was announced:) never used for anything other then testing though.

⤋ Read More
ABC_horticulture
feeds.twtxt.net
 (3y ago)

‘Game-changer’ deal sees Australian avocados to set sail for India
A free-trade agreement and access to the Indian market of 1.5 billion people is being hailed as “the light at the end of the tunnel” for avocado growers following a recent avo “glut”. ⌘ Read more

⤋ Read More
stigatle
yarn.stigatle.no
 (3y ago)
↳ In-reply-to » 👋 Hey y'all yarners 🤗 -- @darch and I have been discussing in our Weekly Yarn.social call (still ongoing... come join us! 🙏) about the experimental Yarn.social <-> Activity Pub integration/bridge I've been working on... And mostly whether it's even a good idea at al, and if we should continue or not?

And mostly whether it’s even a good idea at al, and if we should continue or not?

I think that activitypub in yarn is a great feature! And also one of the easier ones to set up and get going.
And as I said last week - I think it’s a important features - and will drive adoption.
It is optional as well - so if one does not want it - just not turn that feature on.

I personally was missing the fact that I could not easily follow others before you added activitypub, but now I can choose to follow them, which is great.

⤋ Read More
prologic
twtxt.net
 (3y ago)

📣 Update on Activity Pub: Just a quick update on the Yarn.social <-> Activity Pub (aka Mastodon and others):

  • Can follow other Activity Pub actors ✅
  • Can be followed by other Activity Pub actors ✅
  • Your posts can be seen by Activity Pub actors ✅
  • You can see posts from Activity Pub actors ✅

What does not yet work:

  • Translating replies (aka threading) ❌

⤋ Read More
xuu
txt.sour.is
 (3y ago)

@prologic@twtxt.net I have updated to kinda follow this. It now redirects to other webfingers if the resource has a different hostname. I’m still not sure what I should put multiple services with the same domain name. Like if they were to have conflicting properties.

⤋ Read More
xuu
txt.sour.is
 (3y ago)
↳ In-reply-to » @xuu that doesn't seem to fit the spirit of the spec, at least by my read (I could be wrong obv). The example on Wikipedia's webfinger page,

it seems they are following the URN format of a URI where you just prefix things with colons.

urn:example:apple:pear:plum:cherry

⤋ Read More
xuu
dev.txt.sour.is
 (3y ago)
↳ In-reply-to » @xuu that doesn't seem to fit the spirit of the spec, at least by my read (I could be wrong obv). The example on Wikipedia's webfinger page,

it seems they are following the URN format of a URI where you just prefix things with colons.

urn:example:apple:pear:plum:cherry

⤋ Read More
xuu
txt.sour.is
 (3y ago)
↳ In-reply-to » Trying to wrap my head around webfinger..

@prologic@twtxt.net That was exactly my thought at first too. but what do we put as the rel for salty account? since it is decentralized we dont have a set URL for machines to key off. so for example take the standard response from okta:

# http GET https://example.okta.com/.well-known/webfinger  resource==acct:bob
{
    "links": [
        {
            "href": "https://example.okta.com/sso/idps/OKTA?login_hint=bob#",
            "properties": {
                "okta:idp:type": "OKTA"
            },
            "rel": "http://openid.net/specs/connect/1.0/issuer",
            "titles": {
                "und": "example"
            }
        }
    ],
    "subject": "acct:bob"
}

It gives one link that follows the OpenID login. So the details are specific to the subject acct:bob.

Mastodons response:

{
  "subject": "acct:xuu@chaos.social",
  "aliases": [
    "https://chaos.social/@xuu",
    "https://chaos.social/users/xuu"
  ],
  "links": [
    {
      "rel": "http://webfinger.net/rel/profile-page",
      "type": "text/html",
      "href": "https://chaos.social/@xuu"
    },
    {
      "rel": "self",
      "type": "application/activity+json",
      "href": "https://chaos.social/users/xuu"
    },
    {
      "rel": "http://ostatus.org/schema/1.0/subscribe"
    }
  ]
}

it supplies a profile page and a self which are both specific to that account.

⤋ Read More
xuu
dev.txt.sour.is
 (3y ago)
↳ In-reply-to » Trying to wrap my head around webfinger..

@prologic@twtxt.net That was exactly my thought at first too. but what do we put as the rel for salty account? since it is decentralized we dont have a set URL for machines to key off. so for example take the standard response from okta:

# http GET https://example.okta.com/.well-known/webfinger  resource==acct:bob
{
    "links": [
        {
            "href": "https://example.okta.com/sso/idps/OKTA?login_hint=bob#",
            "properties": {
                "okta:idp:type": "OKTA"
            },
            "rel": "http://openid.net/specs/connect/1.0/issuer",
            "titles": {
                "und": "example"
            }
        }
    ],
    "subject": "acct:bob"
}

It gives one link that follows the OpenID login. So the details are specific to the subject acct:bob.

Mastodons response:

{
  "subject": "acct:xuu@chaos.social",
  "aliases": [
    "https://chaos.social/@xuu",
    "https://chaos.social/users/xuu"
  ],
  "links": [
    {
      "rel": "http://webfinger.net/rel/profile-page",
      "type": "text/html",
      "href": "https://chaos.social/@xuu"
    },
    {
      "rel": "self",
      "type": "application/activity+json",
      "href": "https://chaos.social/users/xuu"
    },
    {
      "rel": "http://ostatus.org/schema/1.0/subscribe"
    }
  ]
}

it supplies a profile page and a self which are both specific to that account.

⤋ Read More