reiver to PostFreely • 2Y
#PostFreely Archetypes?
**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 ( [@reiver@mastodon.social](https://mastodon.social/users/reiver) ) --- cc: [@mathew@universeodon.com](https://universeodon.com/users/mathew) [@whylamb@aus.social](https://aus.social/users/whylamb) [@SrRochardBunson@universeodon.com](https://universeodon.com/users/SrRochardBunson) --- #PostFreely
19
4
#PostFreely Archetypes?
reiver to PostFreely • 2Y
**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 ( [@reiver@mastodon.social](https://mastodon.social/users/reiver) ) --- cc: [@mathew@universeodon.com](https://universeodon.com/users/mathew) [@whylamb@aus.social](https://aus.social/users/whylamb) [@SrRochardBunson@universeodon.com](https://universeodon.com/users/SrRochardBunson) --- #PostFreely
19
reiver to PostFreely • 2Y
[Request-For-Comments] PostFreely: Password Reset
I am investigating improving **password resetting** in the PostFreely applications. PostFreely inherited limited **password reset** abilities. I am now looking at improving this. And making it so that PostFreely has a more comprehensive set of methods for resetting passwords. **Please reply with your comments, questions, complaints, and any other feedback.** --- A basic operation of many (maybe most) applications is _signing-in_. There are many different techniques an application could offer its users to enable them to _sign-in_. --- For example — * e-mail address and one-time auth-code (sent to said e-mail address), * finger-print recognition, * user ID & time-based one-time password, --- PostFreely currently does something different. Currently PostFreely offers a popular, well-known method for its users to use to sign-in — * e-mail address & password. --- A trade-off with using passwords, as PostFreely does, is that people sometimes forget their passwords. A solution to this problem is — **resetting a user's password**. --- Currently PostFreely only has two methods for resetting the password: 1. a technical sysop with access to the command-line on the server uses the `postfreely` executable file to interactively reset the user's password to some value, 2. an administrator uses a web-based method to reset a user's password. --- Some problems with this are — * currently a user cannot reset their own password, * currently an administrator's password cannot be reset — if they or someone else cannot directly access the server, or if they are not comfortable using a terminal-emulator, * currently there are _not_ any good ways of automating password resets via 3rd party tools. --- ## Plan PostFreely should have a more comprehensive set of methods to reset passwords — * a user should be able to reset their own password from the web-site, * a technical sysop should have a non-interactive way to reset a user's password from the command-line, so that it lends itself to automation, * a special API should exist for resetting any password including the admin, so that a technical sysop can use it for automation, * (special care needs to be paid attention on how to secure this.) --- **Please reply with your comments, questions, complaints, and any other feedback.** --- ⸺ Charles Iliya Krempeaux ( [@reiver@mastodon.social](https://mastodon.social/users/reiver) )
7
3
[Request-For-Comments] PostFreely: Password Reset
reiver to PostFreely • 2Y
I am investigating improving **password resetting** in the PostFreely applications. PostFreely inherited limited **password reset** abilities. I am now looking at improving this. And making it so that PostFreely has a more comprehensive set of methods for resetting passwords. **Please reply with your comments, questions, complaints, and any other feedback.** --- A basic operation of many (maybe most) applications is _signing-in_. There are many different techniques an application could offer its users to enable them to _sign-in_. --- For example — * e-mail address and one-time auth-code (sent to said e-mail address), * finger-print recognition, * user ID & time-based one-time password, --- PostFreely currently does something different. Currently PostFreely offers a popular, well-known method for its users to use to sign-in — * e-mail address & password. --- A trade-off with using passwords, as PostFreely does, is that people sometimes forget their passwords. A solution to this problem is — **resetting a user's password**. --- Currently PostFreely only has two methods for resetting the password: 1. a technical sysop with access to the command-line on the server uses the `postfreely` executable file to interactively reset the user's password to some value, 2. an administrator uses a web-based method to reset a user's password. --- Some problems with this are — * currently a user cannot reset their own password, * currently an administrator's password cannot be reset — if they or someone else cannot directly access the server, or if they are not comfortable using a terminal-emulator, * currently there are _not_ any good ways of automating password resets via 3rd party tools. --- ## Plan PostFreely should have a more comprehensive set of methods to reset passwords — * a user should be able to reset their own password from the web-site, * a technical sysop should have a non-interactive way to reset a user's password from the command-line, so that it lends itself to automation, * a special API should exist for resetting any password including the admin, so that a technical sysop can use it for automation, * (special care needs to be paid attention on how to secure this.) --- **Please reply with your comments, questions, complaints, and any other feedback.** --- ⸺ Charles Iliya Krempeaux ( [@reiver@mastodon.social](https://mastodon.social/users/reiver) )
7
reiver to PostFreelyEnglish • 2Y
PostFreely Update (2023-10-01)
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 ( [@mathew@universeodon.com](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 ( [@whylamb@aus.social](https://aus.social/@whylamb) ) encouraged myself ( [@reiver@mastodon.social](https://mastodon.social/@reiver) ) and Mathew ( [@mathew@universeodon.com](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 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 --- ## Development Work Mathew ( [@mathew@universeodon.com](https://universeodon.com/@mathew) ) and I ( [@reiver@mastodon.social](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 * by posting on the Fediverse using the `#PostFreely` hash-tag, * or by directly reaching out to us: [@reiver@mastodon.social](https://mastodon.social/@reiver) [@mathew@universeodon.com](https://universeodon.com/@mathew) --- ⸺ Charles Iliya Krempeaux ( [@reiver@mastodon.social](https://mastodon.social/@reiver) )
6
6
PostFreely Update (2023-10-01)
reiver to PostFreelyEnglish • 2Y
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 ( [@mathew@universeodon.com](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 ( [@whylamb@aus.social](https://aus.social/@whylamb) ) encouraged myself ( [@reiver@mastodon.social](https://mastodon.social/@reiver) ) and Mathew ( [@mathew@universeodon.com](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 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 --- ## Development Work Mathew ( [@mathew@universeodon.com](https://universeodon.com/@mathew) ) and I ( [@reiver@mastodon.social](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 * by posting on the Fediverse using the `#PostFreely` hash-tag, * or by directly reaching out to us: [@reiver@mastodon.social](https://mastodon.social/@reiver) [@mathew@universeodon.com](https://universeodon.com/@mathew) --- ⸺ Charles Iliya Krempeaux ( [@reiver@mastodon.social](https://mastodon.social/@reiver) )
6
@reiver ⊼ (Charles) :batman: to Fediverse UX • 2Y
UX problem with Join-Lemmy.org

files.mastodon.social

UX problem with Join-Lemmy.org [@fediverseux](https://flamewar.social/c/fediverseux) “We need a better site to link to than join-lemmy.org. It should concisely pitch lemmy to everyday users and suggest an instance for them to sign up at. Don’t get into the weeds about federation or choosing instances or selecting apps. Just select a sane default and point people to it. Rotate defaults to avoid overloading a given instance or making it too powerful.” [https://lemmy.ml/comment/4353933](https://lemmy.ml/comment/4353933) [https://lemm.ee/post/9881418](https://lemm.ee/post/9881418) [\#FediverseUX](https://mastodon.social/tags/FediverseUX) [#Lemmy](https://mastodon.social/tags/Lemmy) [#Threadiverse](https://mastodon.social/tags/Threadiverse)
3
2
UX problem with Join-Lemmy.org

files.mastodon.social

@reiver ⊼ (Charles) :batman: to Fediverse UX • 2Y
UX problem with Join-Lemmy.org [@fediverseux](https://flamewar.social/c/fediverseux) “We need a better site to link to than join-lemmy.org. It should concisely pitch lemmy to everyday users and suggest an instance for them to sign up at. Don’t get into the weeds about federation or choosing instances or selecting apps. Just select a sane default and point people to it. Rotate defaults to avoid overloading a given instance or making it too powerful.” [https://lemmy.ml/comment/4353933](https://lemmy.ml/comment/4353933) [https://lemm.ee/post/9881418](https://lemm.ee/post/9881418) [\#FediverseUX](https://mastodon.social/tags/FediverseUX) [#Lemmy](https://mastodon.social/tags/Lemmy) [#Threadiverse](https://mastodon.social/tags/Threadiverse)
3
@reiver ⊼ (Charles) :batman: to PostFreely • 2Y
PostFreely in the News: Blogging Resurgence

files.mastodon.social

PostFreely in the News: Blogging Resurgence [@postfreely](https://flamewar.social/c/postfreely) PostFreely got mentioned in the news, along with WriteFreely & WordPress. [https://fediversereport.com/last-week-in-fediverse-episode-37/](https://fediversereport.com/last-week-in-fediverse-episode-37/) [\#PostFreely](https://mastodon.social/tags/PostFreely) [#WordPress](https://mastodon.social/tags/WordPress) [#WriteFreely](https://mastodon.social/tags/WriteFreely) [#blogging](https://mastodon.social/tags/blogging) [#blogdom](https://mastodon.social/tags/blogdom) [#blogoverse](https://mastodon.social/tags/blogoverse) [#blogosphere](https://mastodon.social/tags/blogosphere)
0
5
PostFreely in the News: Blogging Resurgence

files.mastodon.social

@reiver ⊼ (Charles) :batman: to PostFreely • 2Y
PostFreely in the News: Blogging Resurgence [@postfreely](https://flamewar.social/c/postfreely) PostFreely got mentioned in the news, along with WriteFreely & WordPress. [https://fediversereport.com/last-week-in-fediverse-episode-37/](https://fediversereport.com/last-week-in-fediverse-episode-37/) [\#PostFreely](https://mastodon.social/tags/PostFreely) [#WordPress](https://mastodon.social/tags/WordPress) [#WriteFreely](https://mastodon.social/tags/WriteFreely) [#blogging](https://mastodon.social/tags/blogging) [#blogdom](https://mastodon.social/tags/blogdom) [#blogoverse](https://mastodon.social/tags/blogoverse) [#blogosphere](https://mastodon.social/tags/blogosphere)
0
Massoud to Fediverse UX • 1Y
Draft & Schedule Posts for Later
Draft & Schedule Posts for Later [@fediverseux](https://flamewar.social/c/fediverseux) One feature that is currently missing on PixelFed (and something I wish they had) is the capability to compose a post as a draft and schedule it for later publication. [\#FediverseUX](https://mastodon.social/tags/FediverseUX) [#Pixelfed](https://mastodon.social/tags/Pixelfed) [#draft](https://mastodon.social/tags/draft) [#schedule](https://mastodon.social/tags/schedule) [#MissingFeature](https://mastodon.social/tags/MissingFeature)
2
2
Draft & Schedule Posts for Later
Massoud to Fediverse UX • 1Y
Draft & Schedule Posts for Later [@fediverseux](https://flamewar.social/c/fediverseux) One feature that is currently missing on PixelFed (and something I wish they had) is the capability to compose a post as a draft and schedule it for later publication. [\#FediverseUX](https://mastodon.social/tags/FediverseUX) [#Pixelfed](https://mastodon.social/tags/Pixelfed) [#draft](https://mastodon.social/tags/draft) [#schedule](https://mastodon.social/tags/schedule) [#MissingFeature](https://mastodon.social/tags/MissingFeature)
2
reiver to Fediverse UX • 1Y
Fediverse software designed for a single-user solo usage should make the website’s (root) home-page the user profile page.

![](https://flamewar.social/pictrs/image/9e9f1453-b73e-45ed-8876-332eb39cc02a.png) ( https://mastodon.social/@reiver/110925625473415578 ) Fediverse software designed for a single-user solo usage should make the website's (root) home-page the user profile page. I.e., This: > `https://example.com/` Rather than this: > `https://example.com/＠joeblow`
0
2
Fediverse software designed for a single-user solo usage should make the website’s (root) home-page the user profile page.

reiver to Fediverse UX • 1Y
![](https://flamewar.social/pictrs/image/9e9f1453-b73e-45ed-8876-332eb39cc02a.png) ( https://mastodon.social/@reiver/110925625473415578 ) Fediverse software designed for a single-user solo usage should make the website's (root) home-page the user profile page. I.e., This: > `https://example.com/` Rather than this: > `https://example.com/＠joeblow`
0
reiver to Fediverse UX • 1Y
remote user account cache could take up too much space
Each Fediverse server instance has its own local user accounts. But because they on a federated social-media network (called the Fediverse) with other server instances, each server instance needs some "awareness" of user accounts on other server instances. Part of this "awareness" tends to be **caching** the profiles, bios, avatar images, etc, of user accounts on other server instances — i.e., remote user accounts. Some of these images can be very large. And can cause the cache of remote user accounts to take up a lot of drive space. Which often translates to a higher monthly hosting costs. This could apply to any Fediverse software. But this particular example of it happened to Pixelfed. The conversation started here: ![](https://flamewar.social/pictrs/image/5408d292-0ebc-4802-8814-6b4f2b060bc9.png) https://mastodon.social/@mitexleo@buddyverse.xyz/111152253455206463 I also talked to Basit Ali (from `#SpaceHost`) about it, and he said: !["I noticed it as well when migrating @atomicpoet’s pixelfed instance [to #SpaceHost], the remote avatar cache was like 80% of the storage. Also it wasn’t downsizing the avatars before caching, some avatars were in megabytes."](https://flamewar.social/pictrs/image/c0c1a46d-5bb8-4d1d-84de-702704826fa6.png) There are different ways this could be addressed.
2
3
remote user account cache could take up too much space
reiver to Fediverse UX • 1Y
Each Fediverse server instance has its own local user accounts. But because they on a federated social-media network (called the Fediverse) with other server instances, each server instance needs some "awareness" of user accounts on other server instances. Part of this "awareness" tends to be **caching** the profiles, bios, avatar images, etc, of user accounts on other server instances — i.e., remote user accounts. Some of these images can be very large. And can cause the cache of remote user accounts to take up a lot of drive space. Which often translates to a higher monthly hosting costs. This could apply to any Fediverse software. But this particular example of it happened to Pixelfed. The conversation started here: ![](https://flamewar.social/pictrs/image/5408d292-0ebc-4802-8814-6b4f2b060bc9.png) https://mastodon.social/@mitexleo@buddyverse.xyz/111152253455206463 I also talked to Basit Ali (from `#SpaceHost`) about it, and he said: !["I noticed it as well when migrating @atomicpoet’s pixelfed instance [to #SpaceHost], the remote avatar cache was like 80% of the storage. Also it wasn’t downsizing the avatars before caching, some avatars were in megabytes."](https://flamewar.social/pictrs/image/c0c1a46d-5bb8-4d1d-84de-702704826fa6.png) There are different ways this could be addressed.
2
reiver to Spread Fediverse • 1Y
Fediverse InstallFests
We (of the Fediverse) should take a lesson from Linux (and the LUGs back in the day) and do in-person Fediverse JoinFests. Where we help people join the Fediverse. Similar to the Linux InstallFests decades ago. --- I am old enough to remember when Linux was not yet common. (I started using Linux back in 1996. And have been using some distro of Linux since then.) Back then, Linux User Groups (LUGs) got created in different cities by regular people who were enthusiastic abut Linux — to provide help, support, and community for those who were interested in Linux. (I used to be an active member of VanLUG — the Vancouver Linux User Group.) --- From-time-to-time these local Linux User Groups (LUGs) would put on a Linux InstallFest — An in-person event where people (who weren't using Linux yet, but were interested) would bring their computer to the Linux InstallFest, and someone from the local LUG would help install Linux for them on their computer. This helped spread Linux. We (of the Fediverse) could do something similar. --- We (of the Fediverse) could learn from the Linux User Groups (LUGs). We could have our own version of a Linux InstallFest — a Fediverse JoinFest. An in-person event where people who are interested in the Fediverse, but are having trouble joining — can bring their mobile phone or laptop, and some Fediverse-savvy person (like us) could help them join the Fediverse. We could install a Fediverse app on their mobile phone for them. We could help them pick a server to join. --- ⸺ Charles Iliya Krempeaux ( [@reiver@mastodon.social](https://mastodon.social/@reiver) ) --- (This is a re-post from [[1]](https://mastodon.social/@reiver/111179148569130717) [[2]](https://mastodon.social/@reiver/111179170245516076) [[3]](https://mastodon.social/@reiver/111179177342147088) [[4]](https://mastodon.social/@reiver/111179198790557943) )
0
5
Fediverse InstallFests
reiver to Spread Fediverse • 1Y
We (of the Fediverse) should take a lesson from Linux (and the LUGs back in the day) and do in-person Fediverse JoinFests. Where we help people join the Fediverse. Similar to the Linux InstallFests decades ago. --- I am old enough to remember when Linux was not yet common. (I started using Linux back in 1996. And have been using some distro of Linux since then.) Back then, Linux User Groups (LUGs) got created in different cities by regular people who were enthusiastic abut Linux — to provide help, support, and community for those who were interested in Linux. (I used to be an active member of VanLUG — the Vancouver Linux User Group.) --- From-time-to-time these local Linux User Groups (LUGs) would put on a Linux InstallFest — An in-person event where people (who weren't using Linux yet, but were interested) would bring their computer to the Linux InstallFest, and someone from the local LUG would help install Linux for them on their computer. This helped spread Linux. We (of the Fediverse) could do something similar. --- We (of the Fediverse) could learn from the Linux User Groups (LUGs). We could have our own version of a Linux InstallFest — a Fediverse JoinFest. An in-person event where people who are interested in the Fediverse, but are having trouble joining — can bring their mobile phone or laptop, and some Fediverse-savvy person (like us) could help them join the Fediverse. We could install a Fediverse app on their mobile phone for them. We could help them pick a server to join. --- ⸺ Charles Iliya Krempeaux ( [@reiver@mastodon.social](https://mastodon.social/@reiver) ) --- (This is a re-post from [[1]](https://mastodon.social/@reiver/111179148569130717) [[2]](https://mastodon.social/@reiver/111179170245516076) [[3]](https://mastodon.social/@reiver/111179177342147088) [[4]](https://mastodon.social/@reiver/111179198790557943) )
0
reiver to Fediverse UXEnglish • 1Y
choosing preview image for a video

A request for being able to choose what the preview image is for a video, chosen from the frames in the video. ![](https://flamewar.social/pictrs/image/dfc13bd4-6d47-4840-bab4-0221479c84df.png) https://socel.net/@folduptoys/111216008353147790 I can imagine having editing tools would also be useful. It is also common elsewhere for people to be able to use custom images for preview images.
0
1
choosing preview image for a video

reiver to Fediverse UXEnglish • 1Y
A request for being able to choose what the preview image is for a video, chosen from the frames in the video. ![](https://flamewar.social/pictrs/image/dfc13bd4-6d47-4840-bab4-0221479c84df.png) https://socel.net/@folduptoys/111216008353147790 I can imagine having editing tools would also be useful. It is also common elsewhere for people to be able to use custom images for preview images.
0
reiver to Fediverse UX • 1Y
friction with creating podcast in Castopod because of cover image

It feels like the **create podcast** process in Castopod has some friction. You cannot create a podcast unless you have a **cover image** ready for it. The **cover image** must be at least 1400px × 1400px. How many potential podcasters know they need to have this ahead of time? How many potential podcasters have an image of that size ready? This feels like a place that could cause users to give up, and bounce. ![](https://flamewar.social/pictrs/image/16ed4900-a64f-4d0d-a2ee-c9bf77c9550b.png) Could a default or automatically generated podcast cover image, etc, be used if the user doesn't have one ready?
0
1
friction with creating podcast in Castopod because of cover image

reiver to Fediverse UX • 1Y
It feels like the **create podcast** process in Castopod has some friction. You cannot create a podcast unless you have a **cover image** ready for it. The **cover image** must be at least 1400px × 1400px. How many potential podcasters know they need to have this ahead of time? How many potential podcasters have an image of that size ready? This feels like a place that could cause users to give up, and bounce. ![](https://flamewar.social/pictrs/image/16ed4900-a64f-4d0d-a2ee-c9bf77c9550b.png) Could a default or automatically generated podcast cover image, etc, be used if the user doesn't have one ready?
0
reiver to Fediverse UX • 1Y
no link or hint on how to sign-in from Castopod homepage

When you set-up a new Castopod server, there no link or hint on how to sign-up from Castopod homepage. ![](https://flamewar.social/pictrs/image/3a39a915-53cc-430a-bdcb-efcd4c66fd1a.png) That is _not_ ideal, as it is _not_ clear what to do next. You cannot do anything for your podcast without being able to sign-in. --- The actual sign-in page is at `/cp-auth/login` So, for example, if you Castopod server is a `https://example.com/` then the sign-in page would be at `https://example.com/cp-auth/login` ![](https://flamewar.social/pictrs/image/b7a0edc4-1490-4686-a6b9-2d76d9e69bb5.png)
0
1
no link or hint on how to sign-in from Castopod homepage

reiver to Fediverse UX • 1Y
When you set-up a new Castopod server, there no link or hint on how to sign-up from Castopod homepage. ![](https://flamewar.social/pictrs/image/3a39a915-53cc-430a-bdcb-efcd4c66fd1a.png) That is _not_ ideal, as it is _not_ clear what to do next. You cannot do anything for your podcast without being able to sign-in. --- The actual sign-in page is at `/cp-auth/login` So, for example, if you Castopod server is a `https://example.com/` then the sign-in page would be at `https://example.com/cp-auth/login` ![](https://flamewar.social/pictrs/image/b7a0edc4-1490-4686-a6b9-2d76d9e69bb5.png)
0
@reiver ⊼ (Charles) :batman: to Fediverse UX • 1Y
Mutual Button

files.mastodon.social

Mutual Button The Mastodon web UI has a new feature. When you follow someone and they follow you back, the follow button says: "Mutual". Seems like a nice simple feature that improved the user-experience (UX). [@fediverseux](https://flamewar.social/c/fediverseux) [\#Fediverse](https://mastodon.social/tags/Fediverse) [#FediverseUX](https://mastodon.social/tags/FediverseUX) [#Mastodon](https://mastodon.social/tags/Mastodon)
0
1
Mutual Button

files.mastodon.social

@reiver ⊼ (Charles) :batman: to Fediverse UX • 1Y
Mutual Button The Mastodon web UI has a new feature. When you follow someone and they follow you back, the follow button says: "Mutual". Seems like a nice simple feature that improved the user-experience (UX). [@fediverseux](https://flamewar.social/c/fediverseux) [\#Fediverse](https://mastodon.social/tags/Fediverse) [#FediverseUX](https://mastodon.social/tags/FediverseUX) [#Mastodon](https://mastodon.social/tags/Mastodon)
0
@reiver ⊼ (Charles) :batman: to Spread Fediverse • 10M
Spread Fediverse through Entertainment
Spread Fediverse through Entertainment I have a thesis (related to helping bring more people onto the Fediverse) — №1: Most people are interested in Entertainment. №2: the collective appetite for Entertainment is, in a practical sense, unbounded. Therefore, a (practical) path to help bring more people onto the Fediverse is to increase the amount of Entertainment on the Fediverse. [@spreadfediverse](https://flamewar.social/c/spreadfediverse) [\#SpreadFediverse](https://mastodon.social/tags/SpreadFediverse)
0
1
Spread Fediverse through Entertainment
@reiver ⊼ (Charles) :batman: to Spread Fediverse • 10M
Spread Fediverse through Entertainment I have a thesis (related to helping bring more people onto the Fediverse) — №1: Most people are interested in Entertainment. №2: the collective appetite for Entertainment is, in a practical sense, unbounded. Therefore, a (practical) path to help bring more people onto the Fediverse is to increase the amount of Entertainment on the Fediverse. [@spreadfediverse](https://flamewar.social/c/spreadfediverse) [\#SpreadFediverse](https://mastodon.social/tags/SpreadFediverse)
0
@maltfield@monero.town to Fediverse UX • 1Y
PSA: you can’t delete photos uploaded to Lemmy. So don’t (accidentally) upload a nude. That would be bad 😱

tech.michaelaltfield.net

This article will describe how lemmy instance admins can [purge images from pict-rs](https://tech.michaelaltfield.net/2024/03/04/lemmy-fediverse-gdpr/). | [![Nightmare on Lemmy St - A GDPR Horror Story](https://tech.michaelaltfield.net/wp-content/uploads/sites/5/lemmy-fediverse-gdpr_featuredImage2.jpg)](https://tech.michaelaltfield.net/2024/03/04/lemmy-fediverse-gdpr/) | |:--:| | [Nightmare on Lemmy Street (A Fediverse GDPR Horror Story)](https://tech.michaelaltfield.net/2024/03/04/lemmy-fediverse-gdpr/) | This is (also) a horror story about accidentally [uploading very sensitive data](https://tech.michaelaltfield.net/2024/03/04/lemmy-fediverse-gdpr/) to Lemmy, and the (surprisingly) difficult task of deleting it.
0
1
PSA: you can’t delete photos uploaded to Lemmy. So don’t (accidentally) upload a nude. That would be bad 😱

tech.michaelaltfield.net

@maltfield@monero.town to Fediverse UX • 1Y
This article will describe how lemmy instance admins can [purge images from pict-rs](https://tech.michaelaltfield.net/2024/03/04/lemmy-fediverse-gdpr/). | [![Nightmare on Lemmy St - A GDPR Horror Story](https://tech.michaelaltfield.net/wp-content/uploads/sites/5/lemmy-fediverse-gdpr_featuredImage2.jpg)](https://tech.michaelaltfield.net/2024/03/04/lemmy-fediverse-gdpr/) | |:--:| | [Nightmare on Lemmy Street (A Fediverse GDPR Horror Story)](https://tech.michaelaltfield.net/2024/03/04/lemmy-fediverse-gdpr/) | This is (also) a horror story about accidentally [uploading very sensitive data](https://tech.michaelaltfield.net/2024/03/04/lemmy-fediverse-gdpr/) to Lemmy, and the (surprisingly) difficult task of deleting it.
0