manton
manton
CDN for Micro.blog blogs manton.org
|
Embed
Progress spinner
tkoola
tkoola

@manton ooh, this is very nice of you all! Thank you

|
Embed
Progress spinner
Mtt
Mtt

@manton This is great! Thanks!

|
Embed
Progress spinner
rknightuk
rknightuk

@manton This is great, enabled for my blog now 🎉 Does this apply retroactively or just for new uploads?

|
Embed
Progress spinner
canion
canion

@manton This is interesting and exciting - as being in Australia the load times of images has always been the one major sore point for me with micro.blog. I hope this might speed things up! I assume if one later unchecks the box, the process is reversible?

|
Embed
Progress spinner
odd
odd

@manton Nice! Are the compression the same there, or will it serve uncompressed, but de-EXIFed photos?

|
Embed
Progress spinner
manton
manton

@rknightuk Retroactively too. Might take a minute to update everywhere after first changing the setting, though.

|
Embed
Progress spinner
manton
manton

@canion Yep, easy to disable. The checkbox effectively just changes the URLs used on your blog. Behind the scenes we're storing the uploads so they can be accessed at either your own domain name or the new CDN.

|
Embed
Progress spinner
rknightuk
rknightuk

@manton Wonderful 😊

|
Embed
Progress spinner
canion
canion

@manton Fantastic. Thank you for continuing to invest in and improve the service. I'm a happy customer today!

|
Embed
Progress spinner
manton
manton

@odd Compression is exactly the same. I want to explore serving more photo sizes but for now that's unchanged.

|
Embed
Progress spinner
jaheppler
jaheppler

@manton Fantastic feature, thanks!

|
Embed
Progress spinner
maique
maique

@manton Thank you. Trying it.

|
Embed
Progress spinner
jarrod
jarrod

@manton How exactly does it increase performance? Are the images being stored on different servers if you enable it? Eager to learn!

|
Embed
Progress spinner
manton
manton

@jarrod Yes, different servers. If enabled, images are cached at the CDN from more locations around the world instead of at the core Micro.blog platform servers.

|
Embed
Progress spinner
jarrod
jarrod

@manton Cool! Now, you said that if migrating to another blog host in the future, the personal domain URLs are preferred. But since it can easily be disabled, getting back to those URLs would be a simple as unchecking the box before starting a migration, right?

|
Embed
Progress spinner
manton
manton

@jarrod Yep, that's true! Easy to switch back and forth.

|
Embed
Progress spinner
jarrod
jarrod

@manton 👍 That’s the best kind of option. Well done, and thanks!

|
Embed
Progress spinner
pratik
pratik

@manton How does this affect ownership of the images? Also, as @jarrod mentioned, can you add a reminder/note on the 'migrating to another host' help page to disable this option before moving?

|
Embed
Progress spinner
cdevroe
cdevroe

@manton nice addition!

|
Embed
Progress spinner
manton
manton

@pratik @jarrod I don't consider it a change to ownership. You always own your images. We also ignore the CDN for some exports like the "Blog archive format", so it's mostly a non-issue. Good idea to update the help.

|
Embed
Progress spinner
pratik
pratik

@manton Ok. Glad to hear. I wanted to clarify beyond the technical details. For me, it means - images will load faster :)

|
Embed
Progress spinner
crossingthethreshold
crossingthethreshold

@manton This for me is an example of this conversation. I have the motivation to overcome my lack of tech knowledge here, but it might be something that could put some people off, or just cause them to give the feature a wide berth, even if investigation would cause them to benefit from it.

My question is, what is a Content Delivery Network, CDN, and how might this feature benefit me?

|
Embed
Progress spinner
maique
maique

@crossingthethreshold Not the “techiest” of the group, but I believe it means that photos are stored all over the world and, when people access your blog, the one server that’s closer to the reader will take care of delivering the photos, instead of having them all coming from a single server, probably in the US.

The readers will notice the speed change, mostly if they’re located elsewhere (like I’m am). For photo-heavy blogs, like mine, it can mean actually looking at the photos, instead of giving up because they’re taking so long to load.

Is that it, @manton?

|
Embed
Progress spinner
In reply to
crossingthethreshold
crossingthethreshold

@maique Thank you. That is very helpful. I’ve bookmarked this. @manton

|
Embed
Progress spinner
SimonWoods
SimonWoods

@crossingthethreshold @maique @manton That's a brilliant description, Maique.

|
Embed
Progress spinner
maique
maique

@SimonWoods Hopefully it’s also correct 🤣 @crossingthethreshold @manton

|
Embed
Progress spinner
abc
abc

@manton A good new feature. Thank you.

|
Embed
Progress spinner
abc
abc

@Ddanielson CDN

|
Embed
Progress spinner
manton
manton

@maique Exactly right!

|
Embed
Progress spinner
manton
manton

@crossingthethreshold Yeah, it's a good point... I often post things in my blog that are a lot more technical than what we'd put on the Micro.blog home page, for example. Which can be a problem when my blog feels like the official documentation!

|
Embed
Progress spinner
manton
manton

@shew There are no limits as long as it’s used for blogging. In other words, it shouldn’t be used to back up a computer. But for everyday blogging, photos, podcasting, etc. we will not impose any storage or bandwidth limits so it’s not something people have to worry about.

|
Embed
Progress spinner