I’m all in on @microblog I have transferred all my posts off of Wordpress.com. I need to work on doing the DNS switch this weekend. I took an important step last night and replaced Facebook and Instagram with @microblog and @sunlit in my iPhone dock.

@gilcreque I guess I still need to figure things out. Mentioning other accounts doesn’t have a lookup service so I went blind and I was totally wrong. Also, my photo was squared and I was not expecting that so it cut off the part that was important. Lastly, is there no editing ability?

@gilcreque now I found out that you can’t reply with a photo 🤔

@gilcreque more thoughts on this, mentioning may be something to avoid because when I cross-post it connects to even more random accounts. Replies also seem to stay on Micro.blog so I'll have to keep that in mind.

@gilcreque it's also strange to keep receiving notifications about your own replies.

@gilcreque you can touch on the photo preview before you post to change from square. I think editing posts is only on the MB website.

@ronguest thanks! I saw the adjustment when I went to repost. I didn't realize that preview of the photo was going to be the actual photo. I assumed it just cropped it for preview. Lesson learned.

@gilcreque I had the exact same learning experience.

@gilcreque @ronguest I think this is someting that @manton should put on his list for this next video walkthrough (and/or an idea for a new help article, “Posting Photos”).

(I keep having all these ideas for new Help articles and no time to draft them… :-( )

@gilcreque Awesome job! Welcome! 👏👏

@smokey @manton At times I wish we had a wiki or even a github repository for community collab document creation. Once it was good enough it could join the official help area.

@EddieHinkle thanks!

@ronguest @smokey The entire help site is a public GitHub repository. We can track suggestions there or accept pull requests for changes or new help pages.

@gilcreque Thanks for the feedback. I've been working on an auto-complete for typing usernames. Also agree that it shoudn't notify you about your own replies. That should be a simple fix.

@ronguest @smokey If you want to take anything I put on @til and use it in the repo, go ahead and copy it over.

@manton @smokey That’s good, I made a note of the repo. My initial thinking was of a place where someone could draft up part of a help page and others could add to it. I agree it’s possible in github but it’s not very convenient for that. I wonder if enough people use iWork/iCloud that I could start a draft there and share it for others to collab on before reaching the github stage? 🤔 ☁️

@ronguest You could fork the official repo and create a branch for something you’re thinking about, and others could fork that and collaborate, but it’s definitely not as easy as a wiki. With both Camino and NeoOffice, we/I used wikis extensively for drafting stuff collaboratively, and I agree that kind of workflow works great. Particularly when I don’t have a big block of time to fuss with VCS overhead, I could make some quick wiki edits and still accomplish something….

Actually—doesn’t github include a basic wiki with every repo? It seems like it does, although clicking that link does nothing in the help.micro.blog repo. Maybe @manton could enable the wiki there, or one of us could fork the repo and enable the wiki on our fork?

@ronguest

Maybe manton could enable the wiki there, or one of us could fork the repo and enable the wiki on our fork?

Although that assumes someone other than the repository owner will have edit permissions for the repository wiki, and maybe that won’t be the case?

@smokey @ronguest Interesting suggestion to use the GitHub wiki. By the way, I'm not too worried about incomplete help pages. It's a work in progress so if someone wants to contribute some documentation that I can finish, I'm fine if that's live and helping other people.

@manton So you’re saying you’d rather see a .markdown file drafted in ‘posts’ and submitted via a pull request?

Cc @smokey

@ronguest Yes, for now I think that is ideal to keep the workflow simple. If it becomes too much trouble we can revisit other ideas (or some people can use a wiki or Google Docs or anything else for drafts until they are ready to submit).

@manton I should have some free time this week so I will try to create something as an experiment. I think the Github approach is fine for non-collab efforts.

@ronguest Thanks! Got lots more coming up. :)