application/activity+json in https://webfinger.net/lookup/?resource=sorenpeter@norrebro.space
{
"rel": "self",
"type": "application/activity+json",
"href": "https://norrebro.space/users/sorenpeter"
},
Then it would also make sense to define a Link Relations but should that then link to something like
https://twtxt.dev/webfinger.html where we can describe the spec?
application/activity+json in https://webfinger.net/lookup/?resource=sorenpeter@norrebro.space
{
"rel": "self",
"type": "application/activity+json",
"href": "https://norrebro.space/users/sorenpeter"
},
Then it would also make sense to define a Link Relations but should that then link to something like
https://twtxt.dev/webfinger.html where we can describe the spec?
application/activity+json in https://webfinger.net/lookup/?resource=sorenpeter@norrebro.space
{
"rel": "self",
"type": "application/activity+json",
"href": "https://norrebro.space/users/sorenpeter"
},
Then it would also make sense to define a Link Relations but should that then link to something like
https://twtxt.dev/webfinger.html where we can describe the spec?
application/activity+json in https://webfinger.net/lookup/?resource=sorenpeter@norrebro.space
{
"rel": "self",
"type": "application/activity+json",
"href": "https://norrebro.space/users/sorenpeter"
},
Then it would also make sense to define a Link Relations but should that then link to something like
https://twtxt.dev/webfinger.html where we can describe the spec?
And for people who don't like PHP you can always just go with Added WebFinger support to my email address using one rewrite rule and one static file. or simply putting a static JSON in place for
.well-know/webfinger
And for people who don't like PHP you can always just go with Added WebFinger support to my email address using one rewrite rule and one static file. or simply putting a static JSON in place for
.well-know/webfinger
And for people who don't like PHP you can always just go with Added WebFinger support to my email address using one rewrite rule and one static file. or simply putting a static JSON in place for
.well-know/webfinger
And for people who don't like PHP you can always just go with Added WebFinger support to my email address using one rewrite rule and one static file. or simply putting a static JSON in place for
.well-know/webfinger
2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :DThe .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.
Access to those files are closed to the public.
2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :DThe .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.
Access to those files are closed to the public.
2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :DThe .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.
Access to those files are closed to the public.
2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :DThe .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.
Access to those files are closed to the public.
twtAgent.php was turned off, so try again now. I have uploaded the code to: https://github.com/sorenpeter/twtAgent
twtAgent.php was turned off, so try again now. I have uploaded the code to: https://github.com/sorenpeter/twtAgent
twtAgent.php was turned off, so try again now. I have uploaded the code to: https://github.com/sorenpeter/twtAgent
twtAgent.php was turned off, so try again now. I have uploaded the code to: https://github.com/sorenpeter/twtAgent
<detail><summary>-tag maybe?
<detail><summary>-tag maybe?
<detail><summary>-tag maybe?
<detail><summary>-tag maybe?
Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request.
I'm not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from
twtAgent.php to the acctual twtxt.txtHelp with making Timeline send proper User Agents to others would be much appreciated:)
Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request.
I'm not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from
twtAgent.php to the acctual twtxt.txtHelp with making Timeline send proper User Agents to others would be much appreciated:)
Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request.
I'm not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from
twtAgent.php to the acctual twtxt.txtHelp with making Timeline send proper User Agents to others would be much appreciated:)
Right now it just adds every request to a growing log file, but I have also been working on a way to analyse it, so it only saves the time of the latest request.
I'm not sure how to make it part of timeline itself, since it requeses that you redirect/rewrite from
twtAgent.php to the acctual twtxt.txtHelp with making Timeline send proper User Agents to others would be much appreciated:)
EDIT:
A webmention was send to: https://eapl.mx/timeline/webmention (Status: 202)
EDIT:
A webmention was send to: https://eapl.mx/timeline/webmention (Status: 202)
EDIT:
A webmention was send to: https://eapl.mx/timeline/webmention (Status: 202)
EDIT:
A webmention was send to: https://eapl.mx/timeline/webmention (Status: 202)
@movq There was no time for discussion just after the presentation, but I had a chat with some folks later.
@movq There was no time for discussion just after the presentation, but I had a chat with some folks later.
@movq There was no time for discussion just after the presentation, but I had a chat with some folks later.
@movq There was no time for discussion just after the presentation, but I had a chat with some folks later.
(So I will most likely not be joining the call)
(So I will most likely not be joining the call)