Yes, 100%.
One of the challenges will be getting order information from the buyer to the seller in a way that is consistent and error-free. Item numbers, unit prices, shipping, tax, total due. Without a shopping cart application, sellers might be best served by bundling shipping and tax into the item price. Alternatively, gopher commerce could make use of a purchase order/invoice pattern. That's a bit more work for everyone, but should reduce miscommunication.
It might be worth thinking about some kind of rating system or method for confirming purchases a la Reddit marketplaces. Maybe buyers can create a gopher-accessible file with purchase details and sellers can link to that as a way of building a reputation.
I bought an 1802 kit from TMSI and it could have been done over Gopher. Out-of-band payment and I had to fill out and send an order form. It went really well and I'd definitely do it again. An experiment in this space could be low-stakes; stickers or something. If Gopher is best thought of as an improvement on FTP, Gopher commerce is an improvement on sending an SASE with a dollar bill. I'd try it.
I hope it comes with a stylus.
I love that episode.
Classic.
"Sure, it might take one year to learn the basics, but it's worth it if you ask me -- or anyone who uses Vim."
This can't be true, but it feels true.
One of my faves, for navigating buffers. You are using buffers, right?
nnoremap H :bp<cr>
nnoremap L :bn<cr>
nnoremap gb :ls<cr>:b
nnoremap <Leader>g :e#<CR>
nnoremap <Leader>1 :1b<CR>
nnoremap <Leader>2 :2b<CR>
nnoremap <Leader>3 :3b<CR>
nnoremap <Leader>4 :4b<CR>
nnoremap <Leader>5 :5b<CR>
nnoremap <Leader>6 :6b<CR>
nnoremap <Leader>7 :7b<CR>
nnoremap <Leader>8 :8b<CR>
nnoremap <Leader>9 :9b<CR>
nnoremap <Leader>0 :10b<CR>
Hey, I remember reading your gopher posts. Thanks for writing.
How is gopher centralized?