Mastodon normalizer - Revision history

Adamw: /* Experimenting with normalization */ Refine text

2024-07-19T21:02:40Z

Experimenting with normalization: Refine text

← Older revision		Revision as of 21:02, 19 July 2024
Line 4:		Line 4:

	== Experimenting with normalization ==		== Experimenting with normalization ==
	[[File:Preferences for normalizer v0.2.7.png\|thumb\|Preferences pane]]When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the [https://normalizer.webflux.us/ demo service] using your own Mastodon account and instance.		[[File:Preferences for normalizer v0.2.7.png\|thumb\|Preferences pane]]When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the [https://normalizer.webflux.us/ demo service] using your own Mastodon account and instance, or try out the [https://normalizer.webflux.us/help guided tour] as a guest.

	Preferences currently look this this~~. Expect to see many more options here, since customizability is the main point~~.<div style="clear: both;"></div>		Preferences currently look this this.<div style="clear: both;"></div>
	[[File:Equal height.png\|right\|thumb\|Equal height for each author]]		[[File:Equal height.png\|right\|thumb\|Equal height for each author]]

	The default view is called the "orthogonal" view, which gives each author '''equal vertical space''' in your timeline regardless of how many posts they write.		The default view is called the "orthogonal" view, which gives each author '''equal vertical space''' in your timeline regardless of how many posts they write or how big their attachments.

	A more extreme version of this view is the "Check in" mode which shows ~~exactly~~ one ~~recent~~ post from each account ~~you've subscribed to, in other words normalizing~~ both ~~the~~ vertical and horizontal space ~~to a single square for each person~~.		A more extreme version of this view is the "Check in" mode which shows only one post from each account. This can be seen as a normalization of both vertical and horizontal space.

	<div style="clear: both;"></div>		<div style="clear: both;"></div>

	[[File:Normalizer with focused row.png\|thumb\|Focused and expanded row]]		[[File:Normalizer with focused row.png\|thumb\|Focused and expanded row]]
	~~Since the messages might be any length, it's necessary to make them expandable~~. ~~Focused (clicked) rows are expanded, and you can~~ expand ~~every row at once using~~ by ~~using~~ the "natural" row height preference.		Clicking on a row of posts will expand and focus. To expand all posts by default, choose the "natural" row height preference.

	<div style="clear: both;"></div>		<div style="clear: both;"></div>
Line 22:		Line 22:
	== Time dimension ==		== Time dimension ==
	[[File:Time axis.png\|right\|thumb\|Time axis]]		[[File:Time axis.png\|right\|thumb\|Time axis]]
	~~It's possible to~~ reintroduce ~~time,~~ but at 90 degrees running left to right~~. We're showing all the same cards as a regular timeline view, but rearranged on a grid~~.		If we reintroduce the timeline but with its axis tipped by 90 degrees, we can list all of each author's posts as an isolated strip running from left to right.
	<div style="clear: both;"></div>		<div style="clear: both;"></div>

Line 28:		Line 28:
	So far, this software is the labor of one unpaid person acting on friendly suggestions. Contributions, suggestions or other resources are welcome!		So far, this software is the labor of one unpaid person acting on friendly suggestions. Contributions, suggestions or other resources are welcome!

	Its architecture is a server-side, Elixir [https://hexdocs.pm/phoenix_live_view/welcome.html Phoenix Live View] application authenticated temporarily to act as the user. Posts and tokens are kept in server memory for ~~each~~ session, then forgotten.		Its architecture is a server-side, Elixir [https://hexdocs.pm/phoenix_live_view/welcome.html Phoenix Live View] application which updates the user's browser by sending HTML over a websocket. It's authenticated temporarily to act as the user. Posts and tokens are kept in server memory and kept as state for the session, then forgotten on close.

	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, by local code, coprocess, or remotely-hosted~~.		In the long term, user algorithms will ideally be visually- and script-programmable, and shareable.

	== Resources ==		== Resources ==

Adamw: Undo revision 170 by Adamw (talk): nah

2024-07-15T20:03:12Z

Undo revision 170 by Adamw (talk): nah

← Older revision		Revision as of 20:03, 15 July 2024
Line 4:		Line 4:

	== Experimenting with normalization ==		== Experimenting with normalization ==
	[[File:~~Preferences_for_normalizer_v0~~.2.7.png\|~~right~~\|~~frameless~~]]		[[File:Preferences for normalizer v0.2.7.png\|thumb\|Preferences pane]]When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the [https://normalizer.webflux.us/ demo service] using your own Mastodon account and instance.
	When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the [https://normalizer.webflux.us/ demo service] using your own Mastodon account and instance.

	Preferences currently look this this. Expect to see many more options here, since customizability is the main point.<div style="clear: both;"></div>		Preferences currently look this this. Expect to see many more options here, since customizability is the main point.<div style="clear: both;"></div>
	[[File:Equal height.png\|right\|Equal height for each author~~\|frameless~~]]		[[File:Equal height.png\|right\|thumb\|Equal height for each author]]

	The default view is called the "orthogonal" view, which gives each author '''equal vertical space''' in your timeline regardless of how many posts they write.		The default view is called the "orthogonal" view, which gives each author '''equal vertical space''' in your timeline regardless of how many posts they write.
Line 16:		Line 15:
	<div style="clear: both;"></div>		<div style="clear: both;"></div>

	[[File:Normalizer with focused row.png\|Focused and expanded row~~\|right\|frameless~~]]		[[File:Normalizer with focused row.png\|thumb\|Focused and expanded row]]
	Since the messages might be any length, it's necessary to make them expandable. Focused (clicked) rows are expanded, and you can expand every row at once using by using the "natural" row height preference.		Since the messages might be any length, it's necessary to make them expandable. Focused (clicked) rows are expanded, and you can expand every row at once using by using the "natural" row height preference.

Line 22:		Line 21:

	== Time dimension ==		== Time dimension ==
	[[File:Time axis.png\|right\|Time axis~~\|frameless~~]]		[[File:Time axis.png\|right\|thumb\|Time axis]]
	It's possible to reintroduce time, but at 90 degrees running left to right. We're showing all the same cards as a regular timeline view, but rearranged on a grid.		It's possible to reintroduce time, but at 90 degrees running left to right. We're showing all the same cards as a regular timeline view, but rearranged on a grid.
	<div style="clear: both;"></div>		<div style="clear: both;"></div>

Adamw: try frameless images

2024-07-15T20:00:02Z

try frameless images

← Older revision		Revision as of 20:00, 15 July 2024
Line 4:		Line 4:

	== Experimenting with normalization ==		== Experimenting with normalization ==
	[[File:~~Preferences for normalizer v0~~.2.7.png\|~~thumb~~\|~~Preferences pane~~]]When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the [https://normalizer.webflux.us/ demo service] using your own Mastodon account and instance.		[[File:Preferences_for_normalizer_v0.2.7.png\|right\|frameless]]
			When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the [https://normalizer.webflux.us/ demo service] using your own Mastodon account and instance.

	Preferences currently look this this. Expect to see many more options here, since customizability is the main point.<div style="clear: both;"></div>		Preferences currently look this this. Expect to see many more options here, since customizability is the main point.<div style="clear: both;"></div>
	[[File:Equal height.png\|right~~\|thumb~~\|Equal height for each author]]		[[File:Equal height.png\|right\|Equal height for each author\|frameless]]

	The default view is called the "orthogonal" view, which gives each author '''equal vertical space''' in your timeline regardless of how many posts they write.		The default view is called the "orthogonal" view, which gives each author '''equal vertical space''' in your timeline regardless of how many posts they write.
Line 15:		Line 16:
	<div style="clear: both;"></div>		<div style="clear: both;"></div>

	[[File:Normalizer with focused row.png~~\|thumb~~\|Focused and expanded row]]		[[File:Normalizer with focused row.png\|Focused and expanded row\|right\|frameless]]
	Since the messages might be any length, it's necessary to make them expandable. Focused (clicked) rows are expanded, and you can expand every row at once using by using the "natural" row height preference.		Since the messages might be any length, it's necessary to make them expandable. Focused (clicked) rows are expanded, and you can expand every row at once using by using the "natural" row height preference.

Line 21:		Line 22:

	== Time dimension ==		== Time dimension ==
	[[File:Time axis.png\|right~~\|thumb~~\|Time axis]]		[[File:Time axis.png\|right\|Time axis\|frameless]]
	It's possible to reintroduce time, but at 90 degrees running left to right. We're showing all the same cards as a regular timeline view, but rearranged on a grid.		It's possible to reintroduce time, but at 90 degrees running left to right. We're showing all the same cards as a regular timeline view, but rearranged on a grid.
	<div style="clear: both;"></div>		<div style="clear: both;"></div>

Adamw: focused row

2024-07-15T19:57:01Z

focused row

← Older revision		Revision as of 19:57, 15 July 2024
Line 12:		Line 12:

	A more extreme version of this view is the "Check in" mode which shows exactly one recent post from each account you've subscribed to, in other words normalizing both the vertical and horizontal space to a single square for each person.		A more extreme version of this view is the "Check in" mode which shows exactly one recent post from each account you've subscribed to, in other words normalizing both the vertical and horizontal space to a single square for each person.

			<div style="clear: both;"></div>

			[[File:Normalizer with focused row.png\|thumb\|Focused and expanded row]]
			Since the messages might be any length, it's necessary to make them expandable. Focused (clicked) rows are expanded, and you can expand every row at once using by using the "natural" row height preference.

	<div style="clear: both;"></div>		<div style="clear: both;"></div>

Adamw: how to get involved

2024-07-15T15:36:42Z

how to get involved

← Older revision		Revision as of 15:36, 15 July 2024
Line 4:		Line 4:

	== Experimenting with normalization ==		== Experimenting with normalization ==
	When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the [https://normalizer.webflux.us/ demo service] using your own Mastodon account and instance.		[[File:Preferences for normalizer v0.2.7.png\|thumb\|Preferences pane]]When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the [https://normalizer.webflux.us/ demo service] using your own Mastodon account and instance.

	Preferences currently look this this. Expect to see many more options here, since customizability is the main point.		Preferences currently look this this. Expect to see many more options here, since customizability is the main point.<div style="clear: both;"></div>
	~~[[File:Preferences for normalizer v0.2.7.png\|center\|thumb\|Preferences pane]]~~

	<div style="clear: both;"></div>
	[[File:Equal height.png\|right\|thumb\|Equal height for each author]]		[[File:Equal height.png\|right\|thumb\|Equal height for each author]]

Line 23:		Line 20:
	<div style="clear: both;"></div>		<div style="clear: both;"></div>

	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.		== Development ==
			So far, this software is the labor of one unpaid person acting on friendly suggestions. Contributions, suggestions or other resources are welcome!

			Its architecture is a server-side, Elixir [https://hexdocs.pm/phoenix_live_view/welcome.html Phoenix Live View] application authenticated temporarily to act as the user. Posts and tokens are kept in server memory for each session, then forgotten.

			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, by local code, coprocess, or remotely-hosted.

	== Resources ==		== Resources ==

			=== Get involved ===

			* Try out the [https://normalizer.webflux.us demo site].
			* Read and install the [https://gitlab.com/adamwight/mastodon-normalizer source code].
			* Write to @a@social.wikimedia.de

	=== Similar projects ===		=== Similar projects ===
Line 31:		Line 39:
	* Bluesky's [https://blueskyweb.org/blog/7-27-2023-custom-feeds "marketplace of algorithms"].		* Bluesky's [https://blueskyweb.org/blog/7-27-2023-custom-feeds "marketplace of algorithms"].

	=== Reporting on the topic ===		=== Reporting related to the topic ===

	* Young, Nora (2023-09-08). [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 2023-09-11.		* Young, Nora (2023-09-08). [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 2023-09-11.

	~~== Notes ==~~

	~~<references />~~

Adamw: Adamw moved page Elixir/Mastodon normalizer to Mastodon normalizer: Mainly not about Elixir

2024-07-15T15:21:18Z

Adamw moved page Elixir/Mastodon normalizer to Mastodon normalizer: Mainly not about Elixir

← Older revision		Revision as of 15:21, 15 July 2024
(No difference)

Adamw: Now with screenshots

2024-07-15T15:19:06Z

Now with screenshots

← Older revision		Revision as of 15:19, 15 July 2024
Line 1:		Line 1:
	{{Project\|status=~~beta~~\|url=https://normalizer.webflux.us/}}'''Problem statement:''' Social media amplifies the loudest voices more than is necessary. In real life, we know that a person who speaks often and loudly might be full of good insights, or they might just suffer from an excess of hot air. Either way, we aren't obliged to give this person all of our attention just because they're loud.		{{Project\|status=demo\|url=https://normalizer.webflux.us/\|source=https://gitlab.com/adamwight/mastodon-normalizer}}'''Problem statement:''' Social media amplifies the loudest voices more than is necessary. In real life, we know that a person who speaks often and loudly might be full of good insights, or they might just suffer from an excess of hot air. Either way, we aren't obliged to give this person all of our attention just because they're loud.

	There is rarely any way to deal with this, no alternative between full volume and blocked, to allow us to better hear the quieter voices.		There is rarely any way to deal with this, no alternative between full volume and blocked, to allow us to better hear the quieter voices.
Line 6:		Line 6:
	When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the [https://normalizer.webflux.us/ demo service] using your own Mastodon account and instance.		When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the [https://normalizer.webflux.us/ demo service] using your own Mastodon account and instance.

	Preferences currently look ~~like~~ this:		Preferences currently look this this. Expect to see many more options here, since customizability is the main point.
	[[File:Preferences for normalizer v0.2.7.png\|center\|thumb\|Preferences pane]]		[[File:Preferences for normalizer v0.2.7.png\|center\|thumb\|Preferences pane]]
	~~The main innovation is the "orthogonal" view, which gives each author equal vertical space in your timeline, regardless of how many posts they write.~~
	~~[[File:Equal height.png\|center\|thumb\|Equal height for each author]]~~
	~~If you like the idea, please feel free to borrow [https://gitlab.com/adamwight/mastodon-normalizer the code], help with the project, or reimplement it on your preferred platform.~~

	~~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.~~		<div style="clear: both;"></div>
			[[File:Equal height.png\|right\|thumb\|Equal height for each author]]

	~~In audio engineering one loud instrument can often drown out another softer sound.~~ The ~~standard approach to fix this~~ is ~~to normalize~~ the ~~audio~~, ~~bringing the average loudness~~ of ~~all instruments to the same level~~.		The default view is called the "orthogonal" view, which gives each author '''equal vertical space''' in your timeline regardless of how many posts they write.

	~~As social media readers, we~~'~~re instinctively aware that each voice has its own style~~, ~~conciseness and frequency of posting. We might naturally gravitate towards~~ the ~~bright colors, loud text, frequent posters,~~ and to push back we protect our attention through various strategies: muting the spammiest accounts, automatic filtering, skimming aggressively, and so on. (It's also interesting that these strategies have audio analogies: multitrack mixing, noise reduction and fast-forwarding, respectively.)		A more extreme version of this view is the "Check in" mode which shows exactly one recent post from each account you've subscribed to, in other words normalizing both the vertical and horizontal space to a single square for each person.

	~~The basic normalization suggested by @futurebird is implemented in my demo as the "Check in~~" mode, and it works by showing exactly one recent post from each account you've subscribed to.[[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]]		<div style="clear: both;"></div>
	~~== 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?

	~~One obvious visualization is~~ to ~~put the two dimensions~~ at right ~~angles to one another~~, so a ~~two-dimensional view~~. ~~In my demo this is called~~ "~~Orthogonal~~" ~~mode and you can scroll between authors vertically, then read individual timelines by scrolling horizontally. Let me know what you think, dear reader!~~		== Time dimension ==
			[[File:Time axis.png\|right\|thumb\|Time axis]]
			It's possible to reintroduce time, but at 90 degrees running left to right. We're showing all the same cards as a regular timeline view, but rearranged on a grid.
			<div style="clear: both;"></div>

	~~== Customization ==~~		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.
	Like in a fairy tale, these three experiments—I'm including classic "timeline" with only the time dimension and no normalization—have also satisfied the programming "rule of three" and <ref>Current project status: working on the thing right here in the sentence.</ref>I'm ready to collapse the different feed styles down into something that can be generalized. As a first step, I'll turn the parameters into visual knobs that can be seen and adjusted by the user.

	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 ==		== Resources ==

Adamw: rearrange intro

2024-07-15T14:14:06Z

rearrange intro

← Older revision		Revision as of 14:14, 15 July 2024
Line 1:		Line 1:
	{{Project\|status=beta\|url=https://normalizer.webflux.us/}}~~My crash course in "undirected search" began with two brief but eventful years moonlighting for Jibril Jackson~~'~~s startup HYVE~~, ~~which made me aware~~ of ~~Dunbar's number~~, ~~the limits~~ of ~~how much attention~~ we ~~can pay~~ our ~~friends, and how social media tilts the scales so that the loudest voice is heard most~~.		{{Project\|status=beta\|url=https://normalizer.webflux.us/}}'''Problem statement:''' Social media amplifies the loudest voices more than is necessary. In real life, we know that a person who speaks often and loudly might be full of good insights, or they might just suffer from an excess of hot air. Either way, we aren't obliged to give this person all of our attention just because they're loud.

	When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] as something that comes up regularly in discussions about improving Mastodon, ~~I recognized this as the same perennial problem~~ and ~~decided~~ to ~~give a whack at the proposed solution,~~ to ~~see what it looks like. I'm happy with the results so far! You can try~~ the ~~demo using your own Mastodon account~~.		There is rarely any way to deal with this, no alternative between full volume and blocked, to allow us to better hear the quieter voices.

			== Experimenting with normalization ==
			When @futurebird@sauropods.win mentioned the fun idea of a [https://sauropods.win/@futurebird/109971101661561998 customizable timeline] allowing us to check in on our friends' latest posts, I was excited to see how it might be applied. I'm happy with the results so far! You can login to the [https://normalizer.webflux.us/ demo service] using your own Mastodon account and instance.

			Preferences currently look like this:
			[[File:Preferences for normalizer v0.2.7.png\|center\|thumb\|Preferences pane]]
			The main innovation is the "orthogonal" view, which gives each author equal vertical space in your timeline, regardless of how many posts they write.
			[[File:Equal height.png\|center\|thumb\|Equal height for each author]]
	If you like the idea, please feel free to borrow [https://gitlab.com/adamwight/mastodon-normalizer the code], help with the project, or reimplement it on your preferred platform.		If you like the idea, please feel free to borrow [https://gitlab.com/adamwight/mastodon-normalizer the code], help with the project, or reimplement it on your preferred platform.

	~~== 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 13:		Line 18:
	As social media readers, we're instinctively aware that each voice has its own style, conciseness and frequency of posting. We might naturally gravitate towards the bright colors, loud text, frequent posters, and to push back we protect our attention through various strategies: muting the spammiest accounts, automatic filtering, skimming aggressively, and so on. (It's also interesting that these strategies have audio analogies: multitrack mixing, noise reduction and fast-forwarding, respectively.)		As social media readers, we're instinctively aware that each voice has its own style, conciseness and frequency of posting. We might naturally gravitate towards the bright colors, loud text, frequent posters, and to push back we protect our attention through various strategies: muting the spammiest accounts, automatic filtering, skimming aggressively, and so on. (It's also interesting that these strategies have audio analogies: multitrack mixing, noise reduction and fast-forwarding, respectively.)

	The basic normalization suggested by @futurebird is implemented in my demo as the "Check in" mode, and it works by showing exactly one recent post from each account you've subscribed to.		The basic normalization suggested by @futurebird is implemented in my demo as the "Check in" mode, and it works by showing exactly one recent post from each account you've subscribed to.[[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]]

	== Dimensionality ==		== Dimensionality ==
	[[File:Alcudia,_detalle_de_saetera,_sección_norte,_02.jpg\|thumb\|225x225px\|Feeling lucky?]]		[[File:Alcudia,_detalle_de_saetera,_sección_norte,_02.jpg\|thumb\|225x225px\|Feeling lucky?]]

Adamw: /* Resources */ Link to Bluesky blog post

2023-09-11T21:38:46Z

Resources: Link to Bluesky blog post

← Older revision		Revision as of 21:38, 11 September 2023
Line 30:		Line 30:
	=== Similar projects ===		=== 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.
			* Bluesky's [https://blueskyweb.org/blog/7-27-2023-custom-feeds "marketplace of algorithms"].

	=== Reporting on the topic ===		=== Reporting on the topic ===

Adamw: /* Resources */ include interviewer's name

2023-09-11T21:35:47Z

Resources: include interviewer's name

← Older revision		Revision as of 21:35, 11 September 2023
Line 33:		Line 33:
	=== Reporting on the topic ===		=== 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~~.		* Young, Nora (2023-09-08). [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 2023-09-11.

	== Notes ==		== Notes ==

	<references />		<references />