@reiver @weirdwriter @mathew

I composed this for flamewar.socia thread on "What is #postfreely for?" but I've gotten impatient and posted here first :-) https://indieweb.social/@maphew/111835821153858637

It's probably good posted as a general call out anyway, as the thinking is not app or platform specific. Anyway, some of my 2c.

matt (@[email protected])

**Media**: I don't like that for many #internet #authoring platforms images must be hosted on 3rd party service. This got me looking/thinking once again about *Pages are Folders* and *Media in sqlite* and just generally wondering why internet industry in general has settled for media and text being divorced. Yes housing under the same roof is challenging, but so are typography, word docs, embedded zip archives, and shopping carts. Look what we've done there!

Indieweb.Social

@kalisz79 Z zb3.org będzie jakiś czas spokój, ale ja się i tak migruję z niego.
Przynajmniej z 2 powodów:
1. Utrudniony kontakt z załogą zb3.
2. #WriteFreely jednak mocno ogranicza np. komentarze i interakcje. Jego fork #PostFreely daje jakąś nadzieję na szybszy rozwój, ale to jeszcze plany/wczesna implementacja.

Choć na magazyn.social oparty o /kbin. W tym tygodniu odpalamy. Oprócz tego, że można tam pisać Artykuły w markdown jak na WriteFreely, to oprócz swojego profilu można też zakładać Magazyny, które mają własny adres na web, taki blog, i da się je fajnie dostosować. Przykład ciekawego magazynu na bin.pol.social pokazał Kuba @kubaurbanowicz tutaj -> https://bin.pol.social/m/MiddleEast a tutaj przykład artykułu -> https://bin.pol.social/m/MiddleEast/t/7862/Kto-i-jak-wspolczuje-Palestynczykom

Zwróć uwagę na adresy w sieci. A jak wrzucisz w szukajkę na masto, to widać go w prostszej formie, normalnie lata po fedi.

/kbin ma jeszcze kilka innych zalet: fajne komentarze ładnie powątkowane jak na forum, normalnie odpowiadasz ze swojego profilu kbin, bo do tego ma Notki, czyli jak tootki na #mastodon. WriteFreely jest nieme. I kilka innych jeszcze ale to nie elaborat o kib ;)

Acha, widzisz też, ile było odsłon artykułu (z web). Masz moderację własną itd.
Bo on jest nie tylko pod fedi robiony, ale też by dobrze wyglądał normalnie jako strona.

Zachęcam do rozważenia ;)

Middle East - Bin Pol Social

To wszystko, co się tam dzieje, kotłuje, przewala. Zakładam temat nie dlatego, że jestem ekspertem, ale dlatego, że potrzebuję zrozumieć, uporządkować wiedzę, przekonania, a może czasem i wiarę. Tematu Żydów, judaizmu i pochodnych religii, Żydów i Polaków, Palestyńczyków, historii i teraz wystrzeliwanych...

my super-niche #fediverse question of the day: is #postfreely still a drop-in replacement for #writefreely, (per this comment)? because it sounds kind of great 

/cc @reiver @mathew

PostFreely Update (2023-10-01) - FlameWar

This is a PostFreely update for Sunday October 1st, 2023. (Or maybe Monday October 2nd, 2023 — depending on where you are in the world.) (I’d like to do these updates somewhat regularly, just to keep everyone who is interested up to date.) — ## What Is PostFreely PostFreely is a clean, minimalistic publishing platform — geared towards blogging and long-form writing. PostFreely supports Markdown. And in particular CommonMark, thanks to Mathew ( @[email protected] [https://universeodon.com/@mathew] ). And on top of that — PostFreely is Fediverse software — meaning it can connect with Mastodon, Akkoma, Castopod, Firefish, Friendica, Kbin, Lemmy, Misskey, Pixelfed, Pleroma, Plume, and any other software that supports ActivityPub, WebFinger, and the other technologies that the Fediverse is built on top of. PostFreely is also a publishing platform for the smallnet / smallweb — currently supporting the gopher-protocol, and in the near future also supporting the gemini-protocol / gemtext, the nex-protocol, the mercury-protocol, the finger-protocol, as well as restricted sub-sets of XHTML & HTML. — ## History PostFreely is a fork of WriteFreely. Thank you Matt Baer for creating WriteFreely and making it open-source software. After a discussion on the Fediverse between 3 people, Ynte ( @[email protected] [https://aus.social/@whylamb] ) encouraged myself ( @[email protected] [https://mastodon.social/@reiver] ) and Mathew ( @[email protected] [https://universeodon.com/@mathew] ) to fork WriteFreely. That fork became PostFreely. The name “PostFreely” is an homage to Matt Baer’s WriteFreely. To note its history, and try to give credit where credit it due. — ## Archetypes We had some discussion on who PostFreely is being built for. That discussion happened over here: “PostFreely Archetypes” https://flamewar.social/post/2073 [https://flamewar.social/post/2073] Although this type of quantitative research is ongoing — we now have some clarity over who PostFreely is being built for. (A more comprehensive archetype map document still needs to be created.) — ## Roadmap Backlog Knowing who PostFreely is being built for leads into the next thing — what are we planning to build. What we are planning on building is directly affected by who we are creating PostFreely for. What do those people want? What are their problems? PostFreely should try to solve their problems and address their wants. The PostFreely roadmap is not finalized yet. But we have several items in the backlog. Here they are: * password-resets (from the web-based PostFreely application), * image uploads (with Markdown code for the uploaded image automagically put into the Markdown editor): * image upload via drag-and-drop, * image upload svia copy-and-paste, * image upload via a button (when and if the toolbar is shown), * accessibility improvements, * CommonMark Mardown by default * but can change to other formats, too, in addition to CommonMark Markdown: * the gemini-protocol’s gemtext, * the nex-protocol’s (unnamed) directory document format, * (a subset of) XHTML, * (a subset of) HTML, * etc, * post previewing, * better Fediverse integration: * ability to see Fediverse notifications — favorites, boosts, replies, mentions, etc, * edits of posts get propagated on the Fediverse * plus many other things, too * more smallnet / smallweb support: * gemini-protocol & gemtext * mercury-protocol * nex-protocol * finger-protocol * (the gopher-protocol is already supported) * perhaps others, too * commenting, * being able to have conversations with people who comment to your post, * readers being able to see comments to a post, * comment moderation tools, * ability to turn commenting off (and on), * ability to hide specific comments, * ability to block specific users from commenting, * ability to block anyone from who server instances from commenting, * importing content from other platforms into PostFreely * import from WordPress, * import from WriteFreely, * import from Plume, * improved customization abilities (from terminal and via the web-based PostFreely application), * change favicon, * change fonts, * change skin / theme, * teams * Mastodon client-server API support * the Mastodon client-server API is becoming the defacto client-server API for the Fediverse. PostFreely implementing even part of it instantly makes all sorts of tooling (such as mobile apps) work for PostFreely, too. * being able to subscribe by e-mail, * being able to paywall some content (if desired), * optional micro-blogging to be able to chat with subscribers, * new methods for authentication * in addition to password: * one-time authorization code (OTAC), * magic-link, * passkey, * multi-factor authentication (MFA), * admins * multiple admins * step-down as admin * multi-tenant support, * serving a different domain, * similar to how DNS MX records except uses host-meta, * etc. (This list is not prioritized. Being near to the top or bottom of the list is not meaningful.) Again, these are currently in the PostFreely backlog. We are still discussing them. The roadmap is not finalized yet. But hopefully this gives you some sense of where PostFreely is likely going. If you would like to affect the PostFreely roadmap, please post in the PostFreely forum: https://flamewar.social/c/postfreely [https://flamewar.social/c/postfreely] — ## Development Work Mathew ( @[email protected] [https://universeodon.com/@mathew] ) and I ( @[email protected] [https://mastodon.social/@reiver] ) have been doing clean-up work of the PostFreely source-code. This type of work is necessary to prepare for adding features. Mathew and I had a conversation about how much we want PostFreely to diverge from the WriteFreely code-base. There are trade-offs both ways. There are advantages to keeping it similar — such as being able to pull-in upstream changes from WriteFreely. BUT — it does put constraints on us — and limits how much we can improve things. We are still undecided about this. Mathew has been focusing on CommonMark and Markdown component of PostFreely. He has a plan for how to add post previewing for CommonMark Markdown, and for how to make CommonMark the default format. I have been focusing on password-resets and implementing (parts of) the Mastodon client-server API for PostFreely. — ## Feedback We would love to hear from you. You can talk with us and the PostFreely community: * by replying to this post, * by posting in this community: https://flamewar.social/c/postfreely [https://flamewar.social/c/postfreely] * by posting on the Fediverse using the #PostFreely hash-tag, * or by directly reaching out to us: @[email protected] [https://mastodon.social/@reiver] @[email protected] [https://universeodon.com/@mathew] — ⸺ Charles Iliya Krempeaux ( @[email protected] [https://mastodon.social/@reiver] )

PostFreely in the News: Blogging Resurgence

@postfreely

PostFreely got mentioned in the news, along with WriteFreely & WordPress.

https://fediversereport.com/last-week-in-fediverse-episode-37/

#PostFreely #WordPress #WriteFreely #blogging #blogdom #blogoverse #blogosphere

Last Week in Fediverse – episode 37

Mark Zuckerberg talks about Threads, with implications for the fediverse. Fediseer is a new take on sharing information about server blocks. Tying some trends about Germans and social networks together.

fediversereport.com
PostFreely Update (2023-10-01) - FlameWar

This is a PostFreely update for Sunday October 1st, 2023. (Or maybe Monday October 2nd, 2023 — depending on where you are in the world.) (I’d like to do these updates somewhat regularly, just to keep everyone who is interested up to date.) — ## What Is PostFreely PostFreely is a clean, minimalistic publishing platform — geared towards blogging and long-form writing. PostFreely supports Markdown. And in particular CommonMark, thanks to Mathew ( @[email protected] [https://universeodon.com/@mathew] ). And on top of that — PostFreely is Fediverse software — meaning it can connect with Mastodon, Akkoma, Castopod, Firefish, Friendica, Kbin, Lemmy, Misskey, Pixelfed, Pleroma, Plume, and any other software that supports ActivityPub, WebFinger, and the other technologies that the Fediverse is built on top of. PostFreely is also a publishing platform for the smallnet / smallweb — currently supporting the gopher-protocol, and in the near future also supporting the gemini-protocol / gemtext, the nex-protocol, the mercury-protocol, the finger-protocol, as well as restricted sub-sets of XHTML & HTML. — ## History PostFreely is a fork of WriteFreely. Thank you Matt Baer for creating WriteFreely and making it open-source software. After a discussion on the Fediverse between 3 people, Ynte ( @[email protected] [https://aus.social/@whylamb] ) encouraged myself ( @[email protected] [https://mastodon.social/@reiver] ) and Mathew ( @[email protected] [https://universeodon.com/@mathew] ) to fork WriteFreely. That fork became PostFreely. The name “PostFreely” is an homage to Matt Baer’s WriteFreely. To note its history, and try to give credit where credit it due. — ## Archetypes We had some discussion on who PostFreely is being built for. That discussion happened over here: “PostFreely Archetypes” https://flamewar.social/post/2073 [https://flamewar.social/post/2073] Although this type of quantitative research is ongoing — we now have some clarity over who PostFreely is being built for. (A more comprehensive archetype map document still needs to be created.) — ## Roadmap Backlog Knowing who PostFreely is being built for leads into the next thing — what are we planning to build. What we are planning on building is directly affected by who we are creating PostFreely for. What do those people want? What are their problems? PostFreely should try to solve their problems and address their wants. The PostFreely roadmap is not finalized yet. But we have several items in the backlog. Here they are: * password-resets (from the web-based PostFreely application), * image uploads (with Markdown code for the uploaded image automagically put into the Markdown editor): * image upload via drag-and-drop, * image upload svia copy-and-paste, * image upload via a button (when and if the toolbar is shown), * accessibility improvements, * CommonMark Mardown by default * but can change to other formats, too, in addition to CommonMark Markdown: * the gemini-protocol’s gemtext, * the nex-protocol’s (unnamed) directory document format, * (a subset of) XHTML, * (a subset of) HTML, * etc, * post previewing, * better Fediverse integration: * ability to see Fediverse notifications — favorites, boosts, replies, mentions, etc, * edits of posts get propagated on the Fediverse * plus many other things, too * more smallnet / smallweb support: * gemini-protocol & gemtext * mercury-protocol * nex-protocol * finger-protocol * (the gopher-protocol is already supported) * perhaps others, too * commenting, * being able to have conversations with people who comment to your post, * readers being able to see comments to a post, * comment moderation tools, * ability to turn commenting off (and on), * ability to hide specific comments, * ability to block specific users from commenting, * ability to block anyone from who server instances from commenting, * importing content from other platforms into PostFreely * import from WordPress, * import from WriteFreely, * import from Plume, * improved customization abilities (from terminal and via the web-based PostFreely application), * change favicon, * change fonts, * change skin / theme, * teams * Mastodon client-server API support * the Mastodon client-server API is becoming the defacto client-server API for the Fediverse. PostFreely implementing even part of it instantly makes all sorts of tooling (such as mobile apps) work for PostFreely, too. * being able to subscribe by e-mail, * being able to paywall some content (if desired), * optional micro-blogging to be able to chat with subscribers, * new methods for authentication * in addition to password: * one-time authorization code (OTAC), * magic-link, * passkey, * multi-factor authentication (MFA), * admins * multiple admins * step-down as admin * multi-tenant support, * serving a different domain, * similar to how DNS MX records except uses host-meta, * etc. (This list is not prioritized. Being near to the top or bottom of the list is not meaningful.) Again, these are currently in the PostFreely backlog. We are still discussing them. The roadmap is not finalized yet. But hopefully this gives you some sense of where PostFreely is likely going. If you would like to affect the PostFreely roadmap, please post in the PostFreely forum: https://flamewar.social/c/postfreely [https://flamewar.social/c/postfreely] — ## Development Work Mathew ( @[email protected] [https://universeodon.com/@mathew] ) and I ( @[email protected] [https://mastodon.social/@reiver] ) have been doing clean-up work of the PostFreely source-code. This type of work is necessary to prepare for adding features. Mathew and I had a conversation about how much we want PostFreely to diverge from the WriteFreely code-base. There are trade-offs both ways. There are advantages to keeping it similar — such as being able to pull-in upstream changes from WriteFreely. BUT — it does put constraints on us — and limits how much we can improve things. We are still undecided about this. Mathew has been focusing on CommonMark and Markdown component of PostFreely. He has a plan for how to add post previewing for CommonMark Markdown, and for how to make CommonMark the default format. I have been focusing on password-resets and implementing (parts of) the Mastodon client-server API for PostFreely. — ## Feedback We would love to hear from you. You can talk with us and the PostFreely community: * by replying to this post, * by posting in this community: https://flamewar.social/c/postfreely [https://flamewar.social/c/postfreely] * by posting on the Fediverse using the #PostFreely hash-tag, * or by directly reaching out to us: @[email protected] [https://mastodon.social/@reiver] @[email protected] [https://universeodon.com/@mathew] — ⸺ Charles Iliya Krempeaux ( @[email protected] [https://mastodon.social/@reiver] )

@[email protected] @mathew

#PostFreely is coming along.

Mathew and I are mostly doing low-level stuff still. Stuff that is important to do, but aren't necessarily user-facing features.

Although I started working on password-reset. Which will have parts that are user-facing.

I'm planning on doing it in a way that is similar to the Mastodon API — since the Mastodon API seems to have become the (defacto) standard Fediverse client-server API.

@Coolmccool for long form it’d probably be #WriteFreely or it’s more recent fork #PostFreely (looks like the former hasn’t had any updates in quite some time - no idea whether it was abandoned?).

I don’t know about migration options though.

Assume that people have good intentions. Err on the side of being more transparent.

#PostFreely

From: @reiver
https://mastodon.social/@reiver/111105947915941734

@liaizon @reiver @mathew @whylamb Hey there! Just wanted to let you know that in my initial post, I made it clear that #PostFreely is actually a fork of #WriteFreely. And as you mentioned, none of this would've been possible without the amazing work of @matt.

↩️ Reply to: #PostFreely Archetypes? - FlameWarmenuheartsearchedit-2me…I tend to use mostly text, hyperlinks with emphasis (italics) and bolding where needed. Occasionally I need a table for a list, and an embed to a video. Sometimes.

Markdown is helpful for that once you know it because its universal everywhere.
🗣️ Comments & Reactions 💬 https://flamewar.social/comment/66568

#PostFreely Archetypes? - FlameWar

Who is PostFreely being created for? It is not possible to create an application for everyone. Trying to build an application for everyone effectively means you build it for no one. So there needs to be specific types of people we are building PostFreely for. — In the replies to this post we will list, discuss, and describe the archetypes related to, relevant to, or important to PostFreely. ⚠️ This discussion should try to use “neutral” language in its descriptions. ⚠️ — # Examples For example — One type of person we may be building PostFreely for is — People who use WriteFreely, who like WriteFreely, but wish it had some additional features (such as uploading images, or a way to see replies, etc). Another type of person we may be building PostFreely for is — People who like writing in markdown. Yet another type of person we may be building PostFreely for is — People who want to make their content simultaneously available on the Fediverse and the “smallnet” alt-protocols such as finger, gemini, gopher, HTTP (restricted), mercury, nex, and others. Etc. There are many other types of people relevant to PostFreely. The purpose of this discussion is to list out, describe, and discuss these. We will do that in the replies to this post, rather than trying to list them all out here. — # Archetype The name we give to these types of people is archetype. So — What are the architypes we are creating PostFreely for? What are their problems? What do they want? PostFreely may try to solve some of their problems. PostFreely may try to address some of their wants. — # What is an Archetype > archetypes (noun): an idealized model of a number of similar things. From the point-of-view of industrial-research — an archetype is a model of some aspect of a person shared among many people. (UX people tend to call “archetypes”: “personas”. And marketers tend to call “archetypes”: “segments”. In practice, all 3 of these are very similar concepts.) Some examples of (non-Fediverse and non-PostFreely specific) archetypes include: * father, * mother, * son, * daughter * brother, * sister, * husband, * wife, * gardener, * farmer, * computer programmer, * grocery store cashier, * CEO * CTO * etc. You can also probably already see that an individual could express more than one archetype. For example — a single individual could be — a father, a husband, a brother, a son, a CTO, and a programmer at the same time during a certain span of their life. The archetypes an individual expresses could also change over their life-time too. For example — before someone has a child, they wouldn’t be a father or a mother yet; but after they have a child, they would (also) become a father, or a mother (in addition to whatever other archetypes they express). — In this discussion we will focus on archetypes relevant or important to PostFreely. — # PostFreely Features Features in PostFreely would usually be tied to a problem or want of an archetype. And are not just made up arbitrarily. So understanding the relevant, related, and important archetypes for PostFreely is an important precursor before a roadmap can be created. — # Archetype Discovery Archetypes are discovered. They are not arbitrarily made-up. Usually archetypes are discovered by analyzing quantitative-data. And often the quantitative-data is data you collect yourself. Maybe by interviewing people. Maybe by reading discussions on the Fediverse, on forums, and other places. Etc. (CHARLES NOTE: I have already done research in this area. But like with most research — it is never done, and the research work should be ongoing,) — Let’s discuss. Who is PostFreely being created for? What are the architypes we are creating PostFreely for? What are their problems? What do they want? Please reply with your thoughts. — ⸺ Charles Iliya Krempeaux ( @[email protected] [https://mastodon.social/users/reiver] ) — cc: @[email protected] [https://universeodon.com/users/mathew] @[email protected] [https://aus.social/users/whylamb] @[email protected] [https://universeodon.com/users/SrRochardBunson] — #PostFreely