Hey @dino I think that happens because of this:
Looking forward to the fix to see this for my blog (as well as Dino’s)!
3 Likes
Oh my, I can’t believe I glossed over that. Thanks for pointing that out to me.
2 Likes
I kind of like this! Keeps it minimal and to the point. I would like to see this as theme too.
3 Likes
This is awesome! Can’t wait till it works with the custom domains. I was looking for this for a while now. I would use it as a standard interface. I would have one request though: images and videos and embed should be centered and stretch to text width please. Saw your example here and my OCD got triggered a bit 
.
1 Like
Is WriteFreely/Witere.as not fast enough now? Ditch CSS and go back to pure HTML is not a wise choice. Simple and crude are not the same thing. This experimental feature reminds us, isn’t it urgent to add archiving to writeFreely /write.as? I sincerely hope that WriteFreely continues to be built, as it is missing too many features (comment system, searching, archiving, tag navigation, photo uploading, migration between WriteFreely instances, etc.). Now, it’s time, as you’ve said in the past, to integrate the great existing projects into a more unified and powerful product.
My take on this is that it will eventually replace the convoluted CSS that there is right now, as it is historically/hysterically grown. Future customization could then be based on this new system. Which would make it much cleaner and easier to maintain.
I would agree though, there are still features I would love to see. Maybe I missed it, but I would still like to see some kind of roadmap, to get a sense of direction where the project is going . Feature additional feel unfortunately very random.
2 Likes
What bother me is the lack of the option to disable is (I’m working on a PR to that ), this feature together with a smaller CSS will make a huge difference on page load.
This is great! I will totally use this feature once it works with custom domains!
1 Like
Oh, I just realized something. Do you already know how you want to handle posts without a title? I use my main blog as a “micro blog” and would like to suggest to maybe abbreviate the first line with maybe 3 (or 5) words and an ellipses. If the first line is an embed, like a video or tweet (via iframe or similar), I would suggest to skip it and abbreviate the next line.
That’s right, this is mostly a step on the way to something else.
We do handle titles here like we do in the rest of the app. So if you look at your blog’s metadata, you’ll see we automatically pull out a title for posts that don’t have an explicit one – and it’s close to the logic you’re describing. So we’re reusing that for the post titles here.
And to your earlier comment, images and embeds will be centered in our next update!
Oh yeah, I remember when it changed (to the better). The way it was done before was very long and I was thinking about creating a logic for it in my scripts. Then it changed all out of a sudden and was already the way I wanted it 
Woohoo! 
1 Like
Latest changes are out now!
- Support for custom domain blogs and *.writeas.com blogs
- Centered embeds
- Link to the “full” version from your blog’s footer
I’ve also added this to the Write.as Labs page, where you can now easily open the “tiny page” version of your blog.
5 Likes
Wonderful!
Nice! Activated! . Is it planned to make it configurable as the default view for custom domains in the next version? So, when I go to https://micro.jason.re i would get the tiny view by default? It makes it already so much cleaner
This reminds me of blot’s essay theme. I imagine others would love this too as a theme, @matt.
1 Like
I like this tiny version… fast and to the point.
1 Like
Not sure if it is related, but since I have activated the tiny theme, some of the embeds, for example the youtube embeds, dont work anymore. For example visible here.
It looks like it might have been a coincidence with some other (unknown) issue, maybe something routing related with my Internet provider.
This is really awesome & cute! Thanks
1 Like
Hi, honestly I was writing a note on Pleroma to say how @matt was wholesome and how happy I was to have a pro account here, because I was going to ask for support for the Gopher and Gemini protocols, so it seems relevant to this topic. I’ve been on a 500 MB/month data cap between 2012 and 2014 and it still has consequences on my mental health. I think supporting these protocols could be enough to spare a significant number of users from checking their remaining data plan before being cut from the world for the rest of the month.
A suggestion to convert Markdown’s inline links to Gemini’s block style wouldn’t be more complicated than adding them as footnotes and duplicating the styling, starting with an uppercase letter. So instead of getting:
“Oh, by the way, I’ve posted <a href="https://honeypot.afr.social" pictures from my last trip to Hamburg</a>”
we’d get:
“Oh, by the way, I’ve posted pictures from my last trip to Hamburg [1]
[…]
=> https://honeypot.afr.social [1] Pictures from my last trip to Hamburg”
But this is just a suggestion and I don’t know how much complexity it would add to the WriteFreely software.
Thanks so much for everything, for the software, the platform, the communication…
2 Likes