Did my first live webmention test on monkinetic #webmention #indieweb #goldfrog
Entries for #web
← first ← previous page 2 of 4 next → last →
First Live Webmention Test
This could be an embarrassing failure, preserved for posterity for all time!
this link goes to one of the test pages on webmention.rocks
Update: templates should now support h-card with u-photo better.
Aaron Parecki has a great tutorial on Sending your First Webmention from Scratch#webmention #indieweb
Finished #webmention discovery in #goldfrog, all 23 discovery tests on https://webmention.rocks pass. :)
For my next #indieweb trick: I'm working on adding support for Webmention in #goldfrog.
https://github.com/sivy/goldfrog/issues/9
Client:
- Endpoint discovery (header, link, a)
- Send basic webmentions
- Send "special" webmentions (ie Likes)
Server:
- Provide discovery (header, link, a)
- Receive basic webmentions
- Receive "special" webmentions (ie Likes)
Ultimately I'd like to break out my webmention code into a releasable #golang module that can provide reusable http.Handler functions that can be plugged into any Go mux that supports them.
POSSE is the #IndieWeb acronym for Publish (on your) Own Site, Syndicate Everywhere. It's something I'm playing with in Goldfrog.
A common idiom is to differentiate Notes (small microblog-like posts) from Articles (longer blog posts with a title). Right now Goldfrog has a basic blog Post type, with (ID, Title, Slug, Tags, Body). I'd like to keep the posting experience as simple as possible, so I'm thinking about how to handle something that literally just has a Body (and Tags, because I parse and attach any #hashtags - see? - in the content).
My Posts have an ID, though a uniqueness constraint on the slug means I could use that instead. But Notes don't have a title to "slugify" (it is too a word). Goldfrog also writes every post to the filesystem as a Jekyll-compatible markdown file, so I would need to figure out what format and filename/slug would be appropriate so that they get a permalink.
Url Options
- 2020/01/16/note-ab43f6 unique hash id
- 2020/01/16/note-13:25 HH:MM
Actual Progress
An upcoming build of Goldfrog will support new "kind" of Post, albeit only differentiated by the presence of a title. I've made a few UI and backend changes to support notes:
(SORRY, LOST IMAGE)
- Notes get a slug that is constructed from the string "txt-" + a shortened hash based on the note's content, like
txt-8213d2c - Since notes are short enough to look weird on a typical post-detail page, I created a new "Daily Digest" page on the site that shows only the posts for a given day. This is the default target for the permalink for Notes. The slug is used as the
idattribute on the note, so the link jumps directly to the note on the digest page. This results in a "permalink" like "YYYY-MM-DD/#txt-8213d2c" - The Syndicate options (currently for Twitter and Mastodon) are now enabled by default for notes.
- Clicking the "post form" link takes me to a longer post form with options for a title, custom slug, tags, and a larger content area for writing.
Still to work out
- I'm thinking about implementing Webmentions for Goldfrog, since I control the code.
- I'm still pondering how to connect a post or note with it's syndicated version, to allow likes from this site to propagate to the syndicated site. That feels... harder than I want to dig into right now, but I'll be looking for ideas.
Back towards the IndieWeb: Another aspect to creating my own blogging software: I can finally start implementing some of #indieweb principles I’ve been watching for a while.
One of those is POSSE (Publi
http://173.255.215.158/2020/01/back-towards-the-indieweb
Another aspect to creating my own blogging software: I can finally start implementing some of #indieweb principles I've been watching for a while.
One of those is POSSE (Publish Own Site, Syndicate Everywhere) - which means everything you write starts on your own site, and content is syndicated to the appropriate kinds of sites as desired. This could include things like:
- Articles are syndicated via RSS (done, no brainer)
- Short posts (notes) are automatically or optionally published whole to Twitter, Mastodon, or the microblog of your choice
- Articles are automatically or optionally shared to a microblog site with a link back to your own site
Goldfrog + Twitter
While I generally find Twitter overwhelming and frustrating (not nearly as much so as the less-privileged do), I just finished adding a Twitter cross-poster to #goldfrog. I'll be implementing a Mastodon cross-poster in the next few days (/me waves @ toot.cafe), now that I've figured out and implemented the pattern.
The Twitter cross poster will send the title, some text, and a link back to the post. So, let's see if deploying the new feature worked. :D
Progress today: post editing and deleting, many template updates.
I managed NOT to throw the laptop across the room when figuring out golang html/template :win:
Working on a @TravisCI build pipeline, here’s to again not throwing my laptop
I'm not sure, but I think Userland Manila was the first blog software I used that had the new post form integrated right into the front page. Tonight I got #goldfrog doing the same, and I am SO excited #writefortheweb https://t.co/dEGOZRbPyj
hey #lazyweb help
end of docker file
FROM scratch COPY --from=builder /go/bin/myapp /myapp ENTRYPOINT ["/myapp"]
the this:
standard_init_linux.go:211: exec user process caused "no such file or directory"
what the heck?!
Chris Krycho: Chrome is not the Standard
Chris Krycho wrote a thoughtful post about the state of browser development and web standards, and as developers, the tendency sometimes to see Chrome as the standard for what features browsers should be supporting. Chrome is not the Standard:
> Over the past few years, I've increasingly seen articles with headlines that run something like, "New Feature Coming To the Web"— followed by content which described how Chrome had implemented an experimental new feature. "You’ll be able to use this soon!" has been the promise.
> These are tradeoffs, plain and simple. Chrome ships new features fast, but they're not always stable and they often have performance costs. Safari ships new features on a much slower cadence, but they're usually solid and always perform incredibly well.
> That's what makes the web so great, even when it makes things move more slowly. Sometimes — often, even! — moving more slowly not in the experimental phase but in the finalizing phase makes for a much better outcome overall.
Fellow #webnerds, it's a good read.
RT @aaronpk: As much as I enjoy the benefits of running my own server, I really don't like running my own server #indieweb
← first ← previous page 2 of 4 next → last →