3 ms·

I guess its time to make a blog that's only available to read through ssh now.

by javajosh 2y ago

bovermyer 2y ago
Nothing's stopping you. Or you could just run a blog on the Gemini protocol. Either is fine.
hyperorca 2y ago
You can even start selling coffee there, while you're at it.
- sujayk_33 2y ago
  someone's already doing that LoL
  - tentacleuno 2y ago
    https://terminal.shop https://terminal.shop :)
  - pedrogpimenta 2y ago
    that's the joke
wffurr 2y ago
Do you mean a .plan and .project file for finger?
surfingdino 2y ago
Go mTLS, go hardcore.
anthk 2y ago
SDF has blogs over gopher:// gopher://sdf.org/1/phlogs And often, if not usually, or always, the gopher content outmatches the web sites as maintaing a gopher blog it's dead easy compared to the web. No styles, you can post via a script, images would just placed as a link in the end, or under an images/ directory to be read later.
- thejohnconway 2y ago
  As someone that considers images to be really important to most things I’m interested in, that completely sucks. As does Gemini for that matter. Otherwise I do actually quite like the idea of a protocol that is styled by the user agent, not the creator.
  - anthk 2y ago
    A lot of Gemini clients will inline the images, such as Lagrange. Not an issue as you would have with Gopher.
    - thejohnconway 2y ago
      A lot… but what percentage? I’d want a protocol that recognised the semantic relation of images to text, and clients should follow that.
      - anthk 2y ago
        With Gemini, even with terminal clients you can open the inlined images in a typical blog on a gemini capsule with a fast external viewer, such as sxiv with you just can fullscreen with 'f' and q with 'q'. In the case of gopher, it's either a directory with a gophermap, or a text file with the content. You can't have two at the same time. Using a gophermap directory as a fake text post it's a bit of a hack abusing the 'i' item, and it can look really bad on some older clients.
  - 082349872349872 2y ago
    > the idea of a protocol that is styled by the user agent You mean a markup language styled by the user agent? And it could be served by a stateless request protocol, so all requests are equivalent? We could call them JCML and JCTP, I guess...
    - thejohnconway 2y ago
      You’re being snarky, but here’s a serious answer. I don’t see what relevance statelessness has to do with it, so I’ll leave that aside. The ‘problem’ with HTML is that it’s lacking a lot of features we now realise we want, and at the same time is flexible enough with CSS and JavaScript for people to solve them in their own ways. This had led to a proliferation of approaches, and stuff can’t be automated or make accessible reliably. It also makes creation more complicated than it needs to be.

I guess its time to make a blog that's only available to read through ssh now.

bovermyer 2y ago

Nothing's stopping you. Or you could just run a blog on the Gemini protocol. Either is fine.

hyperorca 2y ago

You can even start selling coffee there, while you're at it.

sujayk_33 2y ago
someone's already doing that LoL
- tentacleuno 2y ago
  https://terminal.shop https://terminal.shop :)
- pedrogpimenta 2y ago
  that's the joke

wffurr 2y ago

Do you mean a .plan and .project file for finger?

surfingdino 2y ago

Go mTLS, go hardcore.

anthk 2y ago

SDF has blogs over gopher:// gopher://sdf.org/1/phlogs And often, if not usually, or always, the gopher content outmatches the web sites as maintaing a gopher blog it's dead easy compared to the web. No styles, you can post via a script, images would just placed as a link in the end, or under an images/ directory to be read later.

thejohnconway 2y ago
As someone that considers images to be really important to most things I’m interested in, that completely sucks. As does Gemini for that matter. Otherwise I do actually quite like the idea of a protocol that is styled by the user agent, not the creator.
- anthk 2y ago
  A lot of Gemini clients will inline the images, such as Lagrange. Not an issue as you would have with Gopher.
  - thejohnconway 2y ago
    A lot… but what percentage? I’d want a protocol that recognised the semantic relation of images to text, and clients should follow that.
    - anthk 2y ago
      With Gemini, even with terminal clients you can open the inlined images in a typical blog on a gemini capsule with a fast external viewer, such as sxiv with you just can fullscreen with 'f' and q with 'q'. In the case of gopher, it's either a directory with a gophermap, or a text file with the content. You can't have two at the same time. Using a gophermap directory as a fake text post it's a bit of a hack abusing the 'i' item, and it can look really bad on some older clients.
- 082349872349872 2y ago
  > the idea of a protocol that is styled by the user agent You mean a markup language styled by the user agent? And it could be served by a stateless request protocol, so all requests are equivalent? We could call them JCML and JCTP, I guess...
  - thejohnconway 2y ago
    You’re being snarky, but here’s a serious answer. I don’t see what relevance statelessness has to do with it, so I’ll leave that aside. The ‘problem’ with HTML is that it’s lacking a lot of features we now realise we want, and at the same time is flexible enough with CSS and JavaScript for people to solve them in their own ways. This had led to a proliferation of approaches, and stuff can’t be automated or make accessible reliably. It also makes creation more complicated than it needs to be.