--? I sometimes try to separate different paragraphs or points with a -- instead of a new line / paragraph break. I don't mind either way, but will amend the PR later when I get back from the tournament, unless you'd like to make the suggested change and I'll just accept it? π
--? I sometimes try to separate different paragraphs or points with a -- instead of a new line / paragraph break. I don't mind either way, but will amend the PR later when I get back from the tournament, unless you'd like to make the suggested change and I'll just accept it? π
--? I sometimes try to separate different paragraphs or points with a -- instead of a new line / paragraph break. I don't mind either way, but will amend the PR later when I get back from the tournament, unless you'd like to make the suggested change and I'll just accept it? π
Also whilst I understand the appeal of
curl url | less to read a feed, I find this a terrible user experience in the first place, yes it should be possible to use UNIX text manipulation tools for feeds, which is why using Twtxt as the "spec" and "transport" of the content is so ideal. -- Should you read feeds this way primarily? Probably not.
Also whilst I understand the appeal of
curl url | less to read a feed, I find this a terrible user experience in the first place, yes it should be possible to use UNIX text manipulation tools for feeds, which is why using Twtxt as the "spec" and "transport" of the content is so ideal. -- Should you read feeds this way primarily? Probably not.
Also whilst I understand the appeal of
curl url | less to read a feed, I find this a terrible user experience in the first place, yes it should be possible to use UNIX text manipulation tools for feeds, which is why using Twtxt as the "spec" and "transport" of the content is so ideal. -- Should you read feeds this way primarily? Probably not.
twtxt client, including support for multi-lines (\u2028), I suppose anyone (even I) could put up a PR that addresses that, it's a trivial 1-line patch.As for your very positively written position and point, absolutely 100% π The fact that some folks write cryptic posts to their Twtxt feed (e.g: the feed that posts geospatial coordinates updates and a status of some reading off a device), or some other formats (rare, but do exit), plain text, Markdown or HTML are all attributes of what the author chooses to write. Probably the only form that would be quite hard to cope with _manually_ would be XML/HTML π€£
twtxt client, including support for multi-lines (\\u2028), I suppose anyone (even I) could put up a PR that addresses that, it's a trivial 1-line patch.As for your very positively written position and point, absolutely 100% π The fact that some folks write cryptic posts to their Twtxt feed (e.g: the feed that posts geospatial coordinates updates and a status of some reading off a device), or some other formats (rare, but do exit), plain text, Markdown or HTML are all attributes of what the author chooses to write. Probably the only form that would be quite hard to cope with _manually_ would be XML/HTML π€£
twtxt client, including support for multi-lines (\u2028), I suppose anyone (even I) could put up a PR that addresses that, it's a trivial 1-line patch.As for your very positively written position and point, absolutely 100% π The fact that some folks write cryptic posts to their Twtxt feed (e.g: the feed that posts geospatial coordinates updates and a status of some reading off a device), or some other formats (rare, but do exit), plain text, Markdown or HTML are all attributes of what the author chooses to write. Probably the only form that would be quite hard to cope with _manually_ would be XML/HTML π€£
twtxt client, including support for multi-lines (\u2028), I suppose anyone (even I) could put up a PR that addresses that, it's a trivial 1-line patch.As for your very positively written position and point, absolutely 100% π The fact that some folks write cryptic posts to their Twtxt feed (e.g: the feed that posts geospatial coordinates updates and a status of some reading off a device), or some other formats (rare, but do exit), plain text, Markdown or HTML are all attributes of what the author chooses to write. Probably the only form that would be quite hard to cope with _manually_ would be XML/HTML π€£
> Recently (research and documentation begun in 2007) I have had sufficient experience with a variety of different types of trolls on the internet (in communities, email lists, wikis, and news stories) that it seemed useful to document, categorize, classify, and provide methods for dealing with each type, towards the goal of identifying and defeating trolls as quickly as possible in the interest of creating and maintaining PositiveCommunities.
May be something good to learn from here π€π
> Recently (research and documentation begun in 2007) I have had sufficient experience with a variety of different types of trolls on the internet (in communities, email lists, wikis, and news stories) that it seemed useful to document, categorize, classify, and provide methods for dealing with each type, towards the goal of identifying and defeating trolls as quickly as possible in the interest of creating and maintaining PositiveCommunities.
May be something good to learn from here π€π
> Recently (research and documentation begun in 2007) I have had sufficient experience with a variety of different types of trolls on the internet (in communities, email lists, wikis, and news stories) that it seemed useful to document, categorize, classify, and provide methods for dealing with each type, towards the goal of identifying and defeating trolls as quickly as possible in the interest of creating and maintaining PositiveCommunities.
May be something good to learn from here π€π
yarn.txt feed and a stripped-down and limited twtxt.txt feed. But I am 98% convinced this wouldn't solve any of the perceived problems, actually I'm 100% certain. Mostly because there are no offered solutions, no actionable feedback, no contributions, just complains and arguments.
yarn.txt feed and a stripped-down and limited twtxt.txt feed. But I am 98% convinced this wouldn't solve any of the perceived problems, actually I'm 100% certain. Mostly because there are no offered solutions, no actionable feedback, no contributions, just complains and arguments.
yarn.txt feed and a stripped-down and limited twtxt.txt feed. But I am 98% convinced this wouldn't solve any of the perceived problems, actually I'm 100% certain. Mostly because there are no offered solutions, no actionable feedback, no contributions, just complains and arguments.
yarnd such that it:1. produced a
twtxt.txt feed that stripped \u2028 so all posts are single-line.2. converted Markdown to "plain text"
3. limited posts to 140 characters
Would this make few that scream and shout the loudest happier that Yarn is more _properly_ using Twtxt? π€ Would Yarn _then_ be considered to be using Twtxt as-it-is/was intended? π€
Of course this would have the side effect of:
- Your longer posts would now be truncated and meaningless.
- Posting links to images would no longer work.
- Threading would no non-existent.
And so we're back to square one, where Twtxt as-it-was-is intended is a spec that whilst on its own useful for a very limited number of use-cases it lacks certain features that make microBlogging and interacting with others viable.
yarnd such that it:1. produced a
twtxt.txt feed that stripped \u2028 so all posts are single-line.2. converted Markdown to "plain text"
3. limited posts to 140 characters
Would this make few that scream and shout the loudest happier that Yarn is more _properly_ using Twtxt? π€ Would Yarn _then_ be considered to be using Twtxt as-it-is/was intended? π€
Of course this would have the side effect of:
- Your longer posts would now be truncated and meaningless.
- Posting links to images would no longer work.
- Threading would no non-existent.
And so we're back to square one, where Twtxt as-it-was-is intended is a spec that whilst on its own useful for a very limited number of use-cases it lacks certain features that make microBlogging and interacting with others viable.
yarnd such that it:1. produced a
twtxt.txt feed that stripped \\u2028 so all posts are single-line.2. converted Markdown to "plain text"
3. limited posts to 140 characters
Would this make few that scream and shout the loudest happier that Yarn is more _properly_ using Twtxt? π€ Would Yarn _then_ be considered to be using Twtxt as-it-is/was intended? π€
Of course this would have the side effect of:
- Your longer posts would now be truncated and meaningless.
- Posting links to images would no longer work.
- Threading would no non-existent.
And so we're back to square one, where Twtxt as-it-was-is intended is a spec that whilst on its own useful for a very limited number of use-cases it lacks certain features that make microBlogging and interacting with others viable.
yarnd such that it:1. produced a
twtxt.txt feed that stripped \u2028 so all posts are single-line.2. converted Markdown to "plain text"
3. limited posts to 140 characters
Would this make few that scream and shout the loudest happier that Yarn is more _properly_ using Twtxt? π€ Would Yarn _then_ be considered to be using Twtxt as-it-is/was intended? π€
Of course this would have the side effect of:
- Your longer posts would now be truncated and meaningless.
- Posting links to images would no longer work.
- Threading would no non-existent.
And so we're back to square one, where Twtxt as-it-was-is intended is a spec that whilst on its own useful for a very limited number of use-cases it lacks certain features that make microBlogging and interacting with others viable.
where none of them work with one another and there's no effective bridging, data or identity portability.
where none of them work with one another and there's no effective bridging, data or identity portability.
where none of them work with one another and there's no effective bridging, data or identity portability.
=> https://files.mills.io/download/Twtxt%20IRC%20Logs%202023-04-14.md=
=> https://files.mills.io/download/Twtxt%20IRC%20Logs%202023-04-14.md=
=> https://files.mills.io/download/Twtxt%20IRC%20Logs%202023-04-14.md=
icon I guess or image.
icon I guess or image.
icon I guess or image.
n
{
"name": "prologic",
"desc": "\"Problems are Solved by Method\" π¦πΊπ¨βπ»π¨βπ¦―πΉβ πβ― π¨βπ©βπ§βπ§π₯ -- James Mills (operator of twtxt.net / creator of Yarn.social π§Ά)",
"key": "kex17m00vqjduqlf6j5xcvtpyhk2zg3shv2x8r5qzyancjlhgl4ytj8slvt7h0",
"links": [
{
"title": "My CV",
"href": "https://prologic.shortcircuit.net.au/"
},
{
"title": "My Projects",
"href": "https://git.mills.io/prologic"
},
{
"title": "My Github profile (@prologic)",
"href": "https://github.com/prologic"
}
],
"items": [
{
"id": "https://yarn.mills.io/permalink/xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa",
"hash": "xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa",
"sig": "3vdKTvI_WGDcM_cUUPGmWHPFpZ9IpORgFkhVFndcxbuUm3XF2w895nEvh2CIA0P3OekfmW6pWQP4wSsXZSCMAA",
"format": "text/markdown",
"time": "2023-04-16T11:04:28+10:00",
"content": "Hello World"
}
]
}
n
{
"name": "prologic",
"desc": "\"Problems are Solved by Method\" π¦πΊπ¨βπ»π¨βπ¦―πΉβ πβ― π¨βπ©βπ§βπ§π₯ -- James Mills (operator of twtxt.net / creator of Yarn.social π§Ά)",
"key": "kex17m00vqjduqlf6j5xcvtpyhk2zg3shv2x8r5qzyancjlhgl4ytj8slvt7h0",
"links": [
{
"title": "My CV",
"href": "https://prologic.shortcircuit.net.au/"
},
{
"title": "My Projects",
"href": "https://git.mills.io/prologic"
},
{
"title": "My Github profile (@prologic)",
"href": "https://github.com/prologic"
}
],
"items": [
{
"id": "https://yarn.mills.io/permalink/xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa",
"hash": "xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa",
"sig": "3vdKTvI_WGDcM_cUUPGmWHPFpZ9IpORgFkhVFndcxbuUm3XF2w895nEvh2CIA0P3OekfmW6pWQP4wSsXZSCMAA",
"format": "text/markdown",
"time": "2023-04-16T11:04:28+10:00",
"content": "Hello World"
}
]
}
n
{
"name": "prologic",
"desc": "\\"Problems are Solved by Method\\" π¦πΊπ¨βπ»π¨βπ¦―πΉβ πβ― π¨βπ©βπ§βπ§π₯ -- James Mills (operator of twtxt.net / creator of Yarn.social π§Ά)",
"key": "kex17m00vqjduqlf6j5xcvtpyhk2zg3shv2x8r5qzyancjlhgl4ytj8slvt7h0",
"links": [
{
"title": "My CV",
"href": "https://prologic.shortcircuit.net.au/"
},
{
"title": "My Projects",
"href": "https://git.mills.io/prologic"
},
{
"title": "My Github profile (@prologic)",
"href": "https://github.com/prologic"
}
],
"items": [
{
"id": "https://yarn.mills.io/permalink/xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa",
"hash": "xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa",
"sig": "3vdKTvI_WGDcM_cUUPGmWHPFpZ9IpORgFkhVFndcxbuUm3XF2w895nEvh2CIA0P3OekfmW6pWQP4wSsXZSCMAA",
"format": "text/markdown",
"time": "2023-04-16T11:04:28+10:00",
"content": "Hello World"
}
]
}
n
{
"name": "prologic",
"desc": "\"Problems are Solved by Method\" π¦πΊπ¨βπ»π¨βπ¦―πΉβ πβ― π¨βπ©βπ§βπ§π₯ -- James Mills (operator of twtxt.net / creator of Yarn.social π§Ά)",
"key": "kex17m00vqjduqlf6j5xcvtpyhk2zg3shv2x8r5qzyancjlhgl4ytj8slvt7h0",
"links": [
{
"title": "My CV",
"href": "https://prologic.shortcircuit.net.au/"
},
{
"title": "My Projects",
"href": "https://git.mills.io/prologic"
},
{
"title": "My Github profile (@prologic)",
"href": "https://github.com/prologic"
}
],
"items": [
{
"id": "https://yarn.mills.io/permalink/xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa",
"hash": "xt2mrjwfmwlh6xrcoom7ywpmg6hdrduy56cvzjoi76ibdjjiycwa",
"sig": "3vdKTvI_WGDcM_cUUPGmWHPFpZ9IpORgFkhVFndcxbuUm3XF2w895nEvh2CIA0P3OekfmW6pWQP4wSsXZSCMAA",
"format": "text/markdown",
"time": "2023-04-16T11:04:28+10:00",
"content": "Hello World"
}
]
}
> If we were to decide to write a new spec/protocol, what would it look like?
Here's my rough draft (_back of paper napkin idea_):
- Feeds are JSON file(s) fetchable by standard HTTP clients over TLS
- WebFinger is used at the root of a user's domain (or multi-user) lookup. e.g:
prologic@mills.io -> https://yarn.mills.io/~prologic.json- Feeds contain similar metadata that we're familiar with: Nick, Avatar, Description, etc
- Feed items are signed with a ED25519 private key. That is all "posts" are cryptographically signed.
- Feed items continue to use content-addressing, but use the full Blake2b Base64 encoded hash.
- Edited feed items produce an "Edited" item so that clients can easily follow Edits.
- Deleted feed items produced a "Deleted" item so that clients can easily delete cached items.
#Yarn.social #Protocol #Ideas
> If we were to decide to write a new spec/protocol, what would it look like?
Here's my rough draft (_back of paper napkin idea_):
- Feeds are JSON file(s) fetchable by standard HTTP clients over TLS
- WebFinger is used at the root of a user's domain (or multi-user) lookup. e.g:
prologic@mills.io -> https://yarn.mills.io/~prologic.json- Feeds contain similar metadata that we're familiar with: Nick, Avatar, Description, etc
- Feed items are signed with a ED25519 private key. That is all "posts" are cryptographically signed.
- Feed items continue to use content-addressing, but use the full Blake2b Base64 encoded hash.
- Edited feed items produce an "Edited" item so that clients can easily follow Edits.
- Deleted feed items produced a "Deleted" item so that clients can easily delete cached items.
#Yarn.social #Protocol #Ideas
> If we were to decide to write a new spec/protocol, what would it look like?
Here's my rough draft (_back of paper napkin idea_):
- Feeds are JSON file(s) fetchable by standard HTTP clients over TLS
- WebFinger is used at the root of a user's domain (or multi-user) lookup. e.g:
prologic@mills.io -> https://yarn.mills.io/~prologic.json- Feeds contain similar metadata that we're familiar with: Nick, Avatar, Description, etc
- Feed items are signed with a ED25519 private key. That is all "posts" are cryptographically signed.
- Feed items continue to use content-addressing, but use the full Blake2b Base64 encoded hash.
- Edited feed items produce an "Edited" item so that clients can easily follow Edits.
- Deleted feed items produced a "Deleted" item so that clients can easily delete cached items.
#Yarn.social #Protocol #Ideas
I am not sure what to do about this. π€ I am quite confident that the hostility and sentiment is not held by all Twtxt users past and present π’
This is a case of a few upset purists who prefer to mock, shame and behave passive aggressively instead of contributing to a healthy discussion and ecosystem.
I am uncertain what Yarn should do here π’
I am not sure what to do about this. π€ I am quite confident that the hostility and sentiment is not held by all Twtxt users past and present π’
This is a case of a few upset purists who prefer to mock, shame and behave passive aggressively instead of contributing to a healthy discussion and ecosystem.
I am uncertain what Yarn should do here π’
I am not sure what to do about this. π€ I am quite confident that the hostility and sentiment is not held by all Twtxt users past and present π’
This is a case of a few upset purists who prefer to mock, shame and behave passive aggressively instead of contributing to a healthy discussion and ecosystem.
I am uncertain what Yarn should do here π’
yarnd doesn't shit a shit what you type for your password π
yarnd doesn't shit a shit what you type for your password π
yarnd doesn't shit a shit what you type for your password π
https://twtxt.net -- I'm also worried that if you have "Skip SSL verification" in your code (from reading @lyse's comments) that things will fail on my pod as I'm pretty sure Cloudflare will chuck a hissy fit at you π€£
https://twtxt.net -- I'm also worried that if you have "Skip SSL verification" in your code (from reading @lyse's comments) that things will fail on my pod as I'm pretty sure Cloudflare will chuck a hissy fit at you π€£
https://twtxt.net -- I'm also worried that if you have "Skip SSL verification" in your code (from reading @lyse's comments) that things will fail on my pod as I'm pretty sure Cloudflare will chuck a hissy fit at you π€£
Companies that use open source component freely without paying for them or contributing back should absolutely be held liable when things go wrong, NOT the open source developers. Why? Because those companies are often exploiting their end-users and often making them pay for something that is largely otherwise free (-some conveniences added on top).
Companies that use open source component freely without paying for them or contributing back should absolutely be held liable when things go wrong, NOT the open source developers. Why? Because those companies are often exploiting their end-users and often making them pay for something that is largely otherwise free (-some conveniences added on top).
Companies that use open source component freely without paying for them or contributing back should absolutely be held liable when things go wrong, NOT the open source developers. Why? Because those companies are often exploiting their end-users and often making them pay for something that is largely otherwise free (-some conveniences added on top).
I find the current situation highlights the fact that large corporations build Paid-for products and services to consumers and makes Millions or Billions of $ Β£ β¬ often without as much as either a) contributing back to open source or the projects from which they borrow and depend on b) or pay for what they use or support it in any financial way.
A large part of the Open Source Model in my view is often confused with "FREE" as in $0, but this is total bullshit. Companies need to understand that reusing a piece of open source software, library or component does not imply it is FREE to you. Companies today DO NOT vet, understand, review or even remotely contribute (_in many cases_) bug fixes, security fixes, etc, of the component they freely take and use and profit from.
I find the current situation highlights the fact that large corporations build Paid-for products and services to consumers and makes Millions or Billions of $ Β£ β¬ often without as much as either a) contributing back to open source or the projects from which they borrow and depend on b) or pay for what they use or support it in any financial way.
A large part of the Open Source Model in my view is often confused with "FREE" as in $0, but this is total bullshit. Companies need to understand that reusing a piece of open source software, library or component does not imply it is FREE to you. Companies today DO NOT vet, understand, review or even remotely contribute (_in many cases_) bug fixes, security fixes, etc, of the component they freely take and use and profit from.
I find the current situation highlights the fact that large corporations build Paid-for products and services to consumers and makes Millions or Billions of $ Β£ β¬ often without as much as either a) contributing back to open source or the projects from which they borrow and depend on b) or pay for what they use or support it in any financial way.
A large part of the Open Source Model in my view is often confused with "FREE" as in $0, but this is total bullshit. Companies need to understand that reusing a piece of open source software, library or component does not imply it is FREE to you. Companies today DO NOT vet, understand, review or even remotely contribute (_in many cases_) bug fixes, security fixes, etc, of the component they freely take and use and profit from.
Key point here: a line has to be drawn.
Right now the EU proposed laws don't distinguish between dangerous software and non-dangerous nor free lowly lone non-paid developer vs. commercial company that profits from open source and has no liability despite making millions or billions.
Key point here: a line has to be drawn.
Right now the EU proposed laws don't distinguish between dangerous software and non-dangerous nor free lowly lone non-paid developer vs. commercial company that profits from open source and has no liability despite making millions or billions.
Key point here: a line has to be drawn.
Right now the EU proposed laws don't distinguish between dangerous software and non-dangerous nor free lowly lone non-paid developer vs. commercial company that profits from open source and has no liability despite making millions or billions.