jack
jack

I keep breaking links and wish I’d do better. write.as/jackbaty/…

|
Embed
Progress spinner
hjertnes
hjertnes

@jack This is one of the things I don't care about

|
Embed
Progress spinner
ericmwalk
ericmwalk

@jack not a bad idea having an everything feed. Then it allows you to try new things and have all of it feed one location. However, it doesn’t solve a problem if you want to drop a service and are not sure what to do with the archived stuff. But it does help with the followers side of things so they can keep up 😄

|
Embed
Progress spinner
canion
canion

@ericmwalk Keeping up with the writing of @jack is a full time pursuit. 🤣🤣

|
Embed
Progress spinner
jack
jack

@ericmwalk Right, when no longer using a service, where does everything go? In some cases I've grabbed a static mirror and put it somewhere else. That doesn't help with broken links, but at least eventually Google catches up.

|
Embed
Progress spinner
amit
amit

@jack Over the years, I have realized that the only things that break for me are images. So, I have decided to keep them separate static server, now.

|
Embed
Progress spinner
pimoore
pimoore

@amit @jack interesting idea, what are you using for this?

|
Embed
Progress spinner
jack
jack

@pimoore For the feed? It's a WordPress plugin installed on the Copingmechanism.com blog. Not the ideal place, but the only WP site I have. www.wprssaggregator.com

|
Embed
Progress spinner
amit
amit

@pimoore I wish I could find a ready solution. But I didn't. So currently it is all custom -- images on S3 served by ngnix. // @jack

|
Embed
Progress spinner
jack
jack

@pimoore But for static images. I use either SmugMug or a static web server on my VPS.

|
Embed
Progress spinner
jack
jack

@pimoore @amit Write.as includes their Snap.as image hosting service, which I'm testing. It's iffy for long-term because if I move from Write.as, I lose snap.as. Convenience vs permanence is always a thing.

|
Embed
Progress spinner
pimoore
pimoore

@amit @jack This is one huge benefit of a self-controlled/hosted static site, as you don’t need to worry about breaking images. Even hosting them on GitHub and pushing out to Netlify or Vercel means they won’t break regardless where you deploy. Obviously this means having to wrangle static site generators and workflows yourself, which may or may not be a good trade off.

|
Embed
Progress spinner
jack
jack

@pimoore Half my problem has been that I waffle between nice, permanent, self-contained static images and using 3rd party image hosting. I don't enjoy the static image workflow, but like you say, it doesn't break.

|
Embed
Progress spinner
In reply to
pimoore
pimoore

@jack I really wish there was a static image workflow with responsive images that didn’t require setting up and maintaining a Rube Goldberg machine. Having to host the images is awkward enough depending on your workflow—though Ulysses will upload to GitHub pages from my previous testing—but anything beyond that in terms of resizing and generating multiple images for different devices seems to have no good solution.

If I were using a full static site I’d probably just skip using images entirely to be honest.

|
Embed
Progress spinner
jack
jack

@pimoore Hugo has some resizing tools but I've never bothered. I just pick a reasonable size and stick with that. Sure is nice to just drag a bunch of images into WordPress or Ghost and have a responsive gallery and slideshow just appear.

|
Embed
Progress spinner
pimoore
pimoore

@jack Very true, this is where the (2?) Micro.blog plugins for image galleries would come in really handy.

|
Embed
Progress spinner