Skip to main content

I just did something a bit interesting: I wrote a long piece and posted it on G+, MeWe, Minds, DreamWidth,...

I just did something a bit interesting: I wrote a long piece and posted it on G+, MeWe, Minds, DreamWidth, LiveJournal, Pluspora, Blogger, and Ello (it's about the Diablo 1 HD Mod).

I wrote it in a Google Doc. Interestingly, G+ did NOT display the formatting; boldfacing and italics. Dreamwidth did, with no problems. So did LiveJournal, which received the post as an automatic crosspost from Dreamwidth.

No formatting came through on MeWe, Minds, Pluspora, or Ello. Blogger displayed the formatting, but eliminated text wrapping; I had to switch to HTML and abandon the formatting (although I could have recreated it; it would just have taken a long time). I find it interesting that the two Google products, G+ and Blogger, couldn't handle the formatting applied by Google Docs!

Now I'll wait and see which ones get the most responses, if any.

Comments

  1. Could you post the URLs to all the versions?

    I take it you just did cut and paste from G-Doc to the data entry form of each platform in a web browser?

    ReplyDelete
  2. AFAIK GDocs can save as HTML, have you tried copying the source from that into Blogger?
    Also, at least when using the Android client, G+ tends to retain some formatting for me when copying rich text from a webpage.

    ReplyDelete
  3. Julian Bond Sure!

    Dreamwidth - bobquasit.dreamwidth.org - bobquasit | Belzebub
    LiveJournal - https://bobquasit.livejournal.com/1169842.html
    MeWe - NOT POSSIBLE
    Pluspora (Diaspora) - https://pluspora.com/posts/173357
    Minds - https://www.minds.com/newsfeed/905674638610022400
    Twitter - https://twitter.com/PMaranci/status/1058943159986782208
    Blogger - http://quasit.blogspot.com/2018/11/diablo-1-hd-belzebub.html
    Facebook - I couldn't find a way to get a link for it to share outside of Facebook. Go figure!

    And yes, I just did a straight copy-and-paste. Oddly enough, Blogger was the absolute worst for that. The other sites at least retained paragraph separations. Blogger just rammed everything together in the biggest goddamned paragraph in history!

    ReplyDelete
  4. Filip H.F. Slagter This was a test, so I treated all of the sites in the same way: just a paste of the Docs version.

    ReplyDelete
  5. My approach to this is to author in Markdown using The One True Editor,[1] then produce necessary endpoint formats via Pandoc. These will ideally be pushed directly at publishing platforms via API or other means, though they're readily copy-pasted, generally with a console clipboard manager.

    This gives me maximum control and flexibility.

    https://pandoc.org

    ________________________________
    Notes:

    1. You know what this means if you know what this means.
    pandoc.org - Pandoc - About pandoc

    ReplyDelete
  6. Karen Peck Pandoc is the shiznit.

    If you do commandline / makefile stuff, I've got an epic Pandoc makefile for all kinds of outputs.

    ReplyDelete
  7. Karen Peck So, this Makefile will produce any of numerous output endpoints (about 20 presently). It will automatically open several of those (HTML, PDF), with the open targets, so: "make openpdf" will compile, then open the PDF in the default viewer (usually Preview).

    OSX / MacOS centric. May require various Homebrew-installed utils. A stashed copy:

    https://pastebin.com/raw/H43MKTCq

    That uses a utility script, img-ref-to-eps.sed:

    https://pastebin.com/raw/J6quT7Mj

    ReplyDelete
  8. Karen Peck Ha!

    The Makefile could use some help in a few specific regards:

    1. It's Mac-centric. I'd like to make it far more Linux-friendly.

    2. It needs to be edited with the specific file being converted. I need to up my Makefile-fu to have it read from the commandline or automatically make all *.md files found.

    Other than that, it's useful and should be reasonably extensible, or serve as the basis (mostly by providing recipes for conversions) for a better alternative.

    ReplyDelete
  9. A lot of social media platforms use tags heavily for discovery; many allow following tags. I mean, Google+'s use of hashtags is a pathetic joke, but for most blogging sites it's crucial. I think a more helpful test would include tags because otherwise...who would ever see the post? Only the people who are following you.

    And it takes time and effort to attain followers. If you're testing a lot of different new platforms, it's just not practical to devote adequate attention to doing that on all of them. And even if you do? It's hard to devote "equal" attention to all of them. Some will inevitably get an advantage over the others just by chance or circumstance.

    But tags...I think that tags are an easy thing to do in an objective fashion. Just replicate the tags on each platform (some require manually adding the tags in a separate field, rather than simply including hashtags in the post text). That way, it's the equal low amount of effort on all of the platforms.

    ReplyDelete
  10. Isaac Kuo an extra test could be to see if there's a limit to the amount of hashtags in a post. I know that for instance Instagram either blocks posting (upon editing an existing post), or silently drops the post body (upon creation of a new post) when it contains too many hashtags.

    ReplyDelete
  11. I know tumblr only looks at the first 5 tags for site-wide search purposes, but it allows any number of tags after that which are still usable by user-specific search. I like that method, since it lets the user organize their own posts in great detail, while not overwhelming users of global tag search.

    ReplyDelete
  12. If I edit them all and add hashtags now, would that work? Or do I have to repost?

    ReplyDelete
  13. I think it would be better to do a completely independent second test. Some platforms display in reverse chronological order by post; others by comment; others use some inscrutable algorithm...hard to have an equal baseline except with a fresh new post.

    ReplyDelete
  14. I'll have to pick out some hashtags, I guess. #Diablo seems an obvious one. Can anyone suggest others?

    ReplyDelete
  15. #D1 #BlizzardEntertainment #BlizzardNorth #hacknslash (or #hackAndSlash) #ActionRPG #ARPG #RPG #RolePlayingGame #SierraEntertainment (if you discuss Hellfire as well) #HDMod #modding #RetroGaming

    ReplyDelete
  16. Peter Maranci Good question, one I've been thinking about.

    I'm spinning ideas on how to come up with reasonably-memorable, but also sufficiently distinctive, hashtags.

    The general problems with hashtags are 1) remembering them, 2) pollution by others, and 3) consistent use.

    I'm looking to use hashtags principally to find references by others after the fact. A keyword/date/tag might work, say, #MaranciDiablo181106 -- your name, the keyword, and date in YYMMDD format. There's no real reason to be century-bound conformant, and the result is reasonably compact. So long as you're looking at people copying and pasting or reposting/resharing content, that should work.

    Maybe front-load: #DiabloMaranci181106

    But play with something like that.

    Ideally I'd have a system that generates sufficiently distinctive hashtags. Not unique, merely useful. And the problem of hashtag stuffing / smurfing tends to be minimmised if you're cycling through hashtags with reasonable frequency. No one tag will be particularly interesting to anyone other than a specifically motivated attacker, unless your content goes spectacularly viral.


    Clarifying on my use case: I'm planning on blogging centrally then distributing content across multiple platforms, most of which offer hashtag search. By searching the distinctively-generated hashtags I should be able to find specific discussion of the post(s). I'm planning on curating from that discussion if possible. Or something like that. System in flux but under consideration.

    ReplyDelete
  17. I made a new version on Google Docs, adding a lot of images and editing the text.

    I tested Google Docs publish to the web option, and it looks awful. A lot of the formatting didn't carry through. What the hell is wrong with Google?

    Anyway, I've put it all into HTML. I was thinking of putting it all up onto my game website, and just posting a blurb and a link on all of the social media sites. But I can't access the FTP, so I have to wait to hear back from my friend who administers the server.

    ReplyDelete
  18. Peter Maranci Are you familiar with git, and have you considered git-based publishing capabilities?

    ReplyDelete
  19. Edward Morbius No. I use (believe it or not) Frontpage Express. And I do some hand-coding of HTML. Taught myself from a book in the early '90s.

    What's git?

    ReplyDelete
  20. Peter Maranci Something somewhat complicated but powerful. Lets you manage your sources (documents) locally then push them out remotely.

    Consider it a topic for later.

    You're running Windows?

    ReplyDelete
  21. Edward Morbius I'm running Windows XP, believe it or not. I have a laptop with Windows 10, but I much prefer my desktop with XP. But I was using PCs well before Windows existed.

    ReplyDelete
  22. Edward Morbius It's kind of amazing that it's still running, isn't it? The system is over ten years old, too. I'll just pick up a new desktop when it fails.

    ReplyDelete
  23. Peter Maranci Using an EoL unsupported OS is unwise.

    ReplyDelete

Post a Comment

New comments on this blog are moderated. If you do not have a Google identity, you are welcome to post anonymously. Your comments will appear here after they have been reviewed. Comments with vulgarity will be rejected.

”go"