Key Points:
1. Linear Feed Problem: Linear feeds present a long list of posts without prioritization, forcing users to scroll endlessly to catch up on friends' content. This can lead to addiction and disengagement.
2. Proposed Alternative (Tree Structure): The daily feed structure organizes posts by day, enabling users to prioritize updates from friends who post infrequently while reducing scrolling effort.
3. Mastodon Experience: The author's experience with Mastodon highlighted its effectiveness in allowing content prioritization and managing social media usage without dependency on algorithms.
4. Challenges and Considerations:
- Implementation Challenges: Creating a daily feed system involves organizing content effectively and ensuring users can prioritize posts.
- Platform Support: Current platforms may not have APIs conducive to such changes, making it difficult to implement without significant technical changes.
- Engagement Metrics: The impact on engagement metrics needs to be considered, as traditional metrics might be misinterpreted in a tree structure.
5. Potential Applications Beyond Social Media: This approach could empower users by giving control over content consumption and aiding in balancing social media use without overwhelming them with information.
6. Future Directions: The author hopes for improvements in alternative platforms' feed systems and engagement metrics, potentially through more interactive content models or changes in APIs.
In conclusion, the article emphasizes the importance of providing users with control over their content consumption, moving away from linear feed
Key Points:
1. Linear Feed Problem: Linear feeds present a long list of posts without prioritization, forcing users to scroll endlessly to catch up on friends' content. This can lead to addiction and disengagement.
2. Proposed Alternative (Tree Structure): The daily feed structure organizes posts by day, enabling users to prioritize updates from friends who post infrequently while reducing scrolling effort.
3. Mastodon Experience: The author's experience with Mastodon highlighted its effectiveness in allowing content prioritization and managing social media usage without dependency on algorithms.
4. Challenges and Considerations:
- Implementation Challenges: Creating a daily feed system involves organizing content effectively and ensuring users can prioritize posts.
- Platform Support: Current platforms may not have APIs conducive to such changes, making it difficult to implement without significant technical changes.
- Engagement Metrics: The impact on engagement metrics needs to be considered, as traditional metrics might be misinterpreted in a tree structure.
5. Potential Applications Beyond Social Media: This approach could empower users by giving control over content consumption and aiding in balancing social media use without overwhelming them with information.
6. Future Directions: The author hopes for improvements in alternative platforms' feed systems and engagement metrics, potentially through more interactive content models or changes in APIs.
In conclusion, the article emphasizes the importance of providing users with control over their content consumption, moving away from linear feed
Wer hat sich zu dieser Meldung diese Knopfauswahl überlegt und dann auch noch die Icons dazu ausgedacht? Und warum hat's das Zertifikat überhaupt schon wieder zerlegt? Und wieso kommt der Dialog direkt wieder in ner Endlosschleife hoch, wenn ich abbreche? Komplettversagen nach Strich und Faden an allen Enden. Allen. Grrr, so viel Hass! Ich schalt besser die Büchse aus.
profile views are layed out! 👌 Thank you!
Is it more an API (more oriented to developers), more oriented to UI/UX/Frontend? Perhaps both?
I'd go with prologic's advice of measuring and prioritizing. Perhaps you have a budget or at least something like "let's see how far can we reach in 6 months", and possibly you won't finish in the time you have (just guessing).
Something that has helped me was defining "Why do you we want to refactor this project?".
Could it be to make it compile on newer versions, or making it easier to grow and scale, or perhaps they are trying to sell that product to another company. Every reason has a different path, IMO.
https://konsole.kde.org/
A screenshot of Konsole where `figlet -c \#ILOVEFS` has been executed, and so it shows that hashtag in an ASCII drawing.
https://konsole.kde.org/
A screenshot of Konsole where `figlet -c \#ILOVEFS` has been executed, and so it shows that hashtag in an ASCII drawing.
2024-08-04T11:24:34Z was the last occurrence of this.
2024-08-04T11:24:34Z was the last occurrence of this.
yarnd here? Hmm? 🤔 I've _thought_ about a "read flag" but I just haven't bothered so far...
yarnd here? Hmm? 🤔 I've _thought_ about a "read flag" but I just haven't bothered so far...
CTRL+R on @mckinley's OP to get the _right_ subject reply after poking at the underlying HTML elements on the page.
CTRL+R on @mckinley's OP to get the _right_ subject reply after poking at the underlying HTML elements on the page.
My first step is to read and understand the tree because there are apps inside other apps call each other. I am very determined to work on a new repository.
My first step is to read and understand the tree because there are apps inside other apps call each other. I am very determined to work on a new repository.
https://www.sqlnoir.com/
#sql
https://www.sqlnoir.com/
#sql
> Warning! It looks like trusted-proxies is not set correctly in this instance's configuration. This may cause rate-limiting issues and, by extension, federation issues.
>
> If you are the instance admin, you should fix this by adding 10.66.66.1/32 to your trusted-proxies.
(WWF quer mais da UE)
Excertos:
"As falhas que a UE tem vindo a cometer, alegam os autores do relatório, prejudicam os esforços de descarbonização e, denunciam ainda, incluem “subsídios aos combustíveis fósseis, licenças gratuitas para poluir para a indústria pesada ao abrigo do regime comunitário de comércio de licenças de emissão, a isenção de impostos para a aviação comercial[...]”."
“O aquecimento a curto prazo (anual) não equivale a uma violação permanente do objectivo do Acordo de Paris de 1,5 graus Celsius, mas esta violação a longo prazo pode ocorrer em breve: segundo o Copérnico [programa europeu de monitorização do clima e atmosfera], se a tendência de aquecimento de 30 anos até Dezembro de 2020 se mantivesse, o aquecimento global atingiria uma média a longo prazo de 1,5 graus Celsius em Janeiro de 2034”, destaca o relatório do WWF. E isso trará consequências dramáticas impossíveis de ignorar."
"Entretanto, na segunda-feira, terminou o prazo oficial para os países entregarem às Nações Unidas os seus planos de redução de emissões de gases com efeito de estufa até 2035. Cerca de 95% dos países não cumpriram a sua obrigação — entre os quais a União Europeia (Portugal incluído, claro)."
https://www.publico.pt/2025/02/11/azul/noticia/clima-ue-ateou-fogo-nao-esperar-paises-bombeiros-2122155
(WWF quer mais da UE)
Excertos:
"As falhas que a UE tem vindo a cometer, alegam os autores do relatório, prejudicam os esforços de descarbonização e, denunciam ainda, incluem “subsídios aos combustíveis fósseis, licenças gratuitas para poluir para a indústria pesada ao abrigo do regime comunitário de comércio de licenças de emissão, a isenção de impostos para a aviação comercial[...]”."
“O aquecimento a curto prazo (anual) não equivale a uma violação permanente do objectivo do Acordo de Paris de 1,5 graus Celsius, mas esta violação a longo prazo pode ocorrer em breve: segundo o Copérnico [programa europeu de monitorização do clima e atmosfera], se a tendência de aquecimento de 30 anos até Dezembro de 2020 se mantivesse, o aquecimento global atingiria uma média a longo prazo de 1,5 graus Celsius em Janeiro de 2034”, destaca o relatório do WWF. E isso trará consequências dramáticas impossíveis de ignorar."
"Entretanto, na segunda-feira, terminou o prazo oficial para os países entregarem às Nações Unidas os seus planos de redução de emissões de gases com efeito de estufa até 2035. Cerca de 95% dos países não cumpriram a sua obrigação — entre os quais a União Europeia (Portugal incluído, claro)."
https://www.publico.pt/2025/02/11/azul/noticia/clima-ue-ateou-fogo-nao-esperar-paises-bombeiros-2122155
Well, I've heard you have plenty of experience with Unit Testing and TDD. Perhaps designing a few tests before refactoring?
I've heard of Snapshot testing, but have never tried it: https://github.com/spatie/phpunit-snapshot-assertions
Also, what kind of refactor are you trying to do?
No, in all seriousness, that's a tough one. Try to figure out the requirements and write tests to cover them. In my experience, if there is no good documention, tests might also be lacking. It goes without saying that you have to understand the code segments first before you can begin to refactor them. Commit even earlier and more often than usual, this will help you bisecting potentially introduced bugs later on. Basically baby steps.
But it also depends on the amount of refactoring required. Maybe just scrap it entirely and start from scratch. This might not be feasible due to e.g. the overall project size, though.
A newsreader without read flags would be totally useless to me. But I also do not subscribe to fire hose feeds, so maybe that's a different story with these. I don't know.
To me, filtering read messages out and only showing new messages is the obvious solution. No need for notifications in my opinion.
There are different approaches with read flags. Personally, I like to explicitly mark messages read or unread. This way, I can think about something and easily come back later to reply. Of course, marking messages read could also happen automatically. All decent mail clients I've used in my life offered even more advanced features, like delayed automatic marking.
All I can say is that I'm super happy with that for years. It works absolutely great for me. The only downside is that I see heaps of new, despite years old messages when a bug causes a feed to be incorrectly updated (https://twtxt.net/twt/tnsuifa). ;-)