Mastodon normalizer: Difference between revisions
try to smooth out the intro to normalization |
→Normalization: Drop in some images; link to recent article |
||
| Line 6: | Line 6: | ||
== Normalization == | == Normalization == | ||
[[File:API_Console_-_VU_Meter_Bridge,_API560_10_Band_EQ,_API550A_3_Band_EQ_(2017-01-05_19.45.22_piqsels.com_en).jpg|thumb|It's all about the volume]] | |||
If one topic or author is much more prolific than another, then the louder channel will tend to draw more attention. This problem is often framed as "signal to noise", but the phrase doesn't quite describe the same problem and would be more accurately applied to spam-filtering. Here we're looking at something more nuanced which we'll call "loudness normalization" in which the voices may be equally important, we simply want to give each voice a fair chance to be heard. | If one topic or author is much more prolific than another, then the louder channel will tend to draw more attention. This problem is often framed as "signal to noise", but the phrase doesn't quite describe the same problem and would be more accurately applied to spam-filtering. Here we're looking at something more nuanced which we'll call "loudness normalization" in which the voices may be equally important, we simply want to give each voice a fair chance to be heard. | ||
| Line 15: | Line 16: | ||
== Dimensionality == | == Dimensionality == | ||
[[File:Alcudia,_detalle_de_saetera,_sección_norte,_02.jpg|thumb|225x225px|Feeling lucky?]] | |||
Playing with the "check in" mode I found that it successfully levels out authors so that everyone gets an equal chance to be seen, however the limitation of one recent post 's a painfully narrow viewport, like watching an orchestra through an arrowslit. How can we cross the broad perspective of multiple, leveled channels with the known strengths of a chronological timeline and its potential to tell a story? | Playing with the "check in" mode I found that it successfully levels out authors so that everyone gets an equal chance to be seen, however the limitation of one recent post 's a painfully narrow viewport, like watching an orchestra through an arrowslit. How can we cross the broad perspective of multiple, leveled channels with the known strengths of a chronological timeline and its potential to tell a story? | ||
| Line 24: | Line 26: | ||
In the long term, the algorithm should be fully flexible and visually-programmable, and there would be a library for sharing your algorithms with others. | In the long term, the algorithm should be fully flexible and visually-programmable, and there would be a library for sharing your algorithms with others. | ||
== | == Resources == | ||
=== Similar projects === | |||
* [https://terhech.de/ebou/ Ebou by Benedikt Terhechte] ([https://github.com/terhechte/Ebou source code]) ([https://sauropods.win/@h_albermann@mastodon.social/109972305658551708 highlighted] by @h_albermann) shows a timeline with a single card for each user, and clicking on a user expands their timeline into a new column. Looks very active as of August 2023. | * [https://terhech.de/ebou/ Ebou by Benedikt Terhechte] ([https://github.com/terhechte/Ebou source code]) ([https://sauropods.win/@h_albermann@mastodon.social/109972305658551708 highlighted] by @h_albermann) shows a timeline with a single card for each user, and clicking on a user expands their timeline into a new column. Looks very active as of August 2023. | ||
=== Reporting on the topic === | |||
* [https://www.cbc.ca/radio/spark/eurpoe-digital-services-act-julia-angwin-1.6960911 "As EU law hopes to rein in Big Tech's algorithms, this reporter wants a 'third path'"]. [https://www.cbc.ca/radio/spark Spark]. Retrieved 11 September 2023. | |||
== Notes == | == Notes == | ||
<references /> | <references /> | ||