Fix links, images, videos, formatting of posts

content/anti-harrasment-tools.md

@@ -3,112 +3,42 @@ Date: 2018-10-05 15:39
 Author: Funkwhale
 Category: Announcement
 Slug: anti-harrasment-tools
+Summary: There is an ongoing discussion on Peertube about adding an option do disable the auto-approval of follows from other servers, as a preventive measure to avoid being harassed. As Funkwhale's maintainer, I feel like I have to take a stance in this discussion, because we will have the same ones for Funkwhale.
 
-There is [an ongoing discussion on PeerTube's issue tracker](https://github.com/Chocobozzz/PeerTube/issues/1179)
-
-about adding an option do disable the auto-approval of follows from other servers, as a preventive
-
-measure to avoid being harassed.
-
-At the moment of writing this, this is *the most commented issue* of the project,
-
-and the discussion feels like a battle.
+There is [an ongoing discussion on PeerTube's issue tracker](https://github.com/Chocobozzz/PeerTube/issues/1179) about adding an option do disable the auto-approval of follows from other servers, as a preventive measure to avoid being harassed. At the moment of writing this, this is *the most commented issue* of the project, and the discussion feels like a battle.
 
 ## On the feature itself
 
-This would be an option to activate on your PeerTube instance, to ensure
-
-only approved instances can follow you and syndicate your content.
-
-This feature is already implemented elsewhere, for instance in Mastodon (at the user level),
-
-and not technically *hard* to implement. There is a de-facto way to do that
-
-on the federation/ActivityPub side. The most complex part is probably
-
-to provide a user interface around that, but even that is technically feasible
+This would be an option to activate on your PeerTube instance, to ensure only approved instances can follow you and syndicate your content. This feature is already implemented elsewhere, for instance in Mastodon (at the user level), and not technically *hard* to implement. There is a de-facto way to do that on the federation/ActivityPub side. The most complex part is probably to provide a user interface around that, but even that is technically feasible and there is nothing inherently hard about it.
 
-and there is nothing inherently hard about it.
-
-The rationale is that harrassers have an easier time harrassing you if they can *easily*
-
-access your content, videos, etc. If we can make it harder for them to access your content,
-
-it will need more effort on their side to cause you trouble.
-
-The feature request in PeerTube is a bit different from what is implemented in Mastodon,
-
-because it's asking for a control at the instance level, with a validation from instance
-
-admins. So it's targeting instances instead of users, but the logic is the same.
+The rationale is that harassers have an easier time harassing you if they can *easily* access your content, videos, etc. If we can make it harder for them to access your content, it will need more effort on their side to cause you trouble. The feature request in PeerTube is a bit different from what is implemented in Mastodon, because it's asking for a control at the instance level, with a validation from instance admins. So it's targeting instances instead of users, but the logic is the same.
 
 ## On the arguments against this feature
 
-Most if not all the arguments developped against this feature are political ones,
-
-not technical ones, and falls in one of this category:
-
-1.  This is against free speech
-2.  This is not effective to fight harassment
-
-If you think that controlling your audience is against free speech, please understand
+Most if not all the arguments developed against this feature are political ones, not technical ones, and falls in one of this category:
 
-there is a huge difference between having something publicly *available*, and having
+1. This is against free speech
+2. This is not effective to fight harassment
 
-something publicly *broadcasted*.
+If you think that controlling your audience is against free speech, please understand there is a huge difference between having something publicly *available*, and having something publicly *broadcasted*.
 
-This is a perfectly valid use case to have a blog were publications are accessible to anyone but not wanting
+This is a perfectly valid use case to have a blog were publications are accessible to anyone but not wanting to have it broadcasted to on every other blog or newspaper. Because you are writing for your audience (which may grow organically), but not for *everyone*. The same goes for a video channel. Also, having this feature implemented means more people will join the network, as they will feel more secure to do so. Everyone benefits from a bigger network with more content.
 
-to have it broadcasted to on every other blog or newspaper. Because you are writing for your
+Now, about the efficacy of this feature. Sure, some people will still be able to bypass that (using RSS feeds or embeds, browsing your instance directly, etc.), but the important bit is *it won't be as easy for them*. Thus, there is a higher chance they will simply leave you alone and go on with their lives.
 
-audience (which may grow organically), but not for *everyone*. The same goes for a video
+It's not the ultimate solution to harassment. But it's definitely a good one to reduce the harassment coming from low-motivation harassers: dropping a hateful comment because they see your content popping in their timelines, sharing it with other harassers, etc.
 
-channel.
-
-Also, having this feature implemented means more people will join the network, as they will
-
-feel more secure to do so. Everyone benefits from a bigger network with more content.
-
-Now, about the efficacity of this feature.
-
-Sure, some people will still be able to bypass that (using RSS feeds or embeds, browsing your instance directly, etc.),
-
-but the important bit is *it won't be as easy for them*. Thus, there is a higher
-
-chance they will simply leave you alone and go on with their lives.
-
-It's not the ultimate solution to harassment. But it's definitely a good one
-
-to reduce the harassment coming from low-motivation harrassers: dropping a hateful
-
-comment because they see your content popping in their timelines, sharing it with
-
-other harrassers, etc.
-
-It's a first step and should be considered as is. I really hope PeerTube contributors
-
-can take this in consideration when deciding whether they should implement it.
+It's a first step and should be considered as is. I really hope PeerTube contributors can take this in consideration when deciding whether they should implement it.
 
 ## On the stance of Funkwhale about anti-harassment tools
 
-As Funkwhale's maintainer, I feel like I have to take a stance in this discussion, because
-
-we will have the same ones for Funkwhale. Here is my stance on the subject:
-
--   Having anti-harrasment features, even if incomplete and/or not 100% effective is better than having nothing
--   I'll happily consider any suggestion to improve the existing anti-harassment features or integrate new ones
+As Funkwhale's maintainer, I feel like I have to take a stance in this discussion, because we will have the same ones for Funkwhale. Here is my stance on the subject:
 
-Apart from manual approval of follows (which is already implemented), there is an
+- Having anti-harrasment features, even if incomplete and/or not 100% effective is better than having nothing
+- I'll happily consider any suggestion to improve the existing anti-harassment features or integrate new ones
 
-[open issue to support block/mute at the actor and instance level](https://code.eliotberriot.com/funkwhale/funkwhale/issues/320)
+Apart from manual approval of follows (which is already implemented), there is an [open issue to support block/mute at the actor and instance level](https://dev.funkwhale.audio/funkwhale/funkwhale/issues/320). This will be included in the first release that support direct interaction between actors, as I expect harassment to become a real problem at that point.
 
-This will be included in the first release that support direct interaction between actors,
-
-as I expect harassment to become a real problem at that point.
-
-On the long-term, I'd also like to experiment with new tools, such as block/mute lists. But we'll need regular
-
-block/mute before that anyway!
+On the long-term, I'd also like to experiment with new tools, such as block/mute lists. But we'll need regular block/mute before that anyway!
 
 There are probably plenty of other options to try as well, so if you want to help shape the moderation and anti-harassment tools for Funkwhale, feel free to say hi!
-

content/blog-post-week-2019-24.md

@@ -3,17 +3,18 @@ Date: 2019-06-14 14:01
 Author: Funkwhale
 Category: Announcement
 Slug: blog-post-week-2019-24
+Summary: Check out what's happened since our last post!
 
-What happened since [last time](https://blog.funkwhale.audio/%7E/Announcements/logbook-week-22-2019-20)?
+What happened since [last time]({filename}logbook-week-22-2019-20.md)?
 
 ## Finalized roadmap for Funkwhale 0.20
 
 We now have a [final roadmap for the 0.20 release](https://governance.funkwhale.audio/d/tjlI6VZa/funkwhale-0-20-roadmap), meaning we can start development. This is the list of new features that will be implemented:
 
--   Easier Discovery of music via genres/tags
--   Admin ability to delete users/content (content is already implemented)
--   Allow-listing
--   Report option on everything
+- Easier Discovery of music via genres/tags
+- Admin ability to delete users/content (content is already implemented)
+- Allow-listing
+- Report option on everything
 
 ## Software development activity
 
@@ -27,44 +28,44 @@ Our first General Assembly took place on May 19th and went very well :)
 
 We voted on many subjects:
 
--   We are now officially named: The Funkwhale Collective
--   We approved our drafted statutes
--   We decided of the membership fees: the chosen membership fee is free, starting with 1€ per year.
--   We elected the candidates for the various decision bodies:
+- We are now officially named: The Funkwhale Collective
+- We approved our drafted statutes
+- We decided of the membership fees: the chosen membership fee is free, starting with 1€ per year.
+- We elected the candidates for the various decision bodies:
 
 **Board**
 
-[\@auzzy](https://blog.funkwhale.audio/@/auzzy/ "auzzy"): president
+@auzzy: president
 
-[\@lindan](https://blog.funkwhale.audio/@/lindan/ "lindan"): treasurer
+@lindan: treasurer
 
-[\@gordon](https://blog.funkwhale.audio/@/gordon/ "gordon"): secretary
+@gordon: secretary
 
 **Steering Commitee**
 
-[\@sporiff](https://blog.funkwhale.audio/@/sporiff/ "sporiff")
+@sporiff
 
-[\@robin](https://blog.funkwhale.audio/@/robin/ "robin")
+@robin
 
-[\@eliotberriot](https://blog.funkwhale.audio/@/eliotberriot/ "eliotberriot")
+@eliotberriot
 
 **Moderation Commitee**
 
-[\@ginnymcqueen](https://blog.funkwhale.audio/@/ginnymcqueen/ "ginnymcqueen")
+@ginnymcqueen
 
-[\@ren](https://blog.funkwhale.audio/@/ren/ "ren")
+@ren
 
 ## Building a group of Code Reviewers
 
 As part of our ongoing effort to transition to a "Benevolent Dictator" to a community-driven governance, we're in the process of building a group of reviewers that are willing to review contributions made to Funkwhale.
 
-Because lots of those contributions are done by [\@eliotberriot](https://blog.funkwhale.audio/@/eliotberriot/ "eliotberriot") , having systematic reviews will reduce the bus factor and ensure the contributions are understood and approved by other community members.
+Because lots of those contributions are done by @eliotberriot, having systematic reviews will reduce the bus factor and ensure the contributions are understood and approved by other community members.
 
 We're maintaining an [open pad](https://pad.funkwhale.audio/code-reviewers) with reviewers name and area of interests, so feel free to add your name to this list :)
 
 ## Naming Betty’s friends
 
-Ginny started a thread [Naming Betty’s friends](https://governance.funkwhale.audio/d/dRgIuPFj/betty-s-thread) where everyone was invited to suggest names for the animals created by Robin and visible on https://funkwhale.audio/
+Ginny started a thread [Naming Betty’s friends](https://governance.funkwhale.audio/d/dRgIuPFj/betty-s-thread) where everyone was invited to suggest names for the animals created by Robin and visible on <https://funkwhale.audio>
 
 So you already know Betty the blue whale and our mascot,
 
@@ -82,11 +83,10 @@ Eliot started a thread [Coordinate translations](https://governance.funkwhale.au
 
 ## Discussions on a future desktop client
 
-Discussions and debates are continuing [in the thread started by](https://governance.funkwhale.audio/d/Ne1wR2jt/a-desktop-client-for-funkwhale) [\@Kaze](https://blog.funkwhale.audio/@/Kaze/ "Kaze") to launch the development of a dedicated, multiplatform desktop client for Funkwhale.
+Discussions and debates are continuing [in the thread started by](https://governance.funkwhale.audio/d/Ne1wR2jt/a-desktop-client-for-funkwhale) @Kaze to launch the development of a dedicated, multiplatform desktop client for Funkwhale.
 
 A poll was opened this week to identify core priorities and features, and will remain opened for a few weeks. If you want to see this happen, remember to cast your vote!
 
-We would like to thank all the Funkwhale community, so many wonderful folks involved in this gread adventure !
+We would like to thank all the Funkwhale community, so many wonderful folks involved in this great adventure !
 
 This article was written by Eliot and Robin.
-

content/blog-post-week-2019-27.md

@@ -3,8 +3,9 @@ Date: 2019-07-08 08:00
 Author: Funkwhale
 Category: Announcement
 Slug: blog-post-week-2019-27
+Summary: Check out what's happened since our last post!
 
-What happened since [last time](https://blog.funkwhale.audio/%7E/Announcements/blog-post-week-26)?
+What happened since [last time]({filename}blog-post-week-26.md)?
 
 ## Retribute website creation
 
@@ -16,7 +17,7 @@ Ginny suggested to address them with a few sentences for each on the front page.
 
 [The very first specification draft for Retribute is now public for review](https://dev.funkwhale.audio/retribute.me/spec/merge_requests/1/), and we're looking for feedback about it.
 
-It's nowhere near complete, but it's a first step to gather some feedback and building a solid, efficent and adequate specification!
+It's nowhere near complete, but it's a first step to gather some feedback and building a solid, efficient and adequate specification!
 
 ## New landing page
 
@@ -43,4 +44,3 @@ If you have some experience as a plugin author and want to contribute to the des
 We got the confirmation from the french authorities and The Funkwhale Collective is now legally a thing!
 
 Next steps are: opening a bank account then communicate with our community so interested individuals can become members of the collective.
-