@eapl.me@eapl.me Sorry to disappoint you. 😅 https://movq.de/v/2c13d7a75c/s.png

You have a microwave oven at home, right?

You can type 3 and 0 for 30 seconds, 100 for a minute (shown as 1:00), or 200 for two minutes (2:00).

What would happen if you type 777 and Start?
A) Nothing
B) Self-destruction
C) Will run for 7 minutes and 77 seconds (boring!)

What about 7777 ?

@lyse@lyse.isobeef.org Ouch 🤕

@sorenpeter@darch.dk Nice 😊

Added support for uploading images to to #Timeline

Image

Right now you need to copy the markdown code yourself, but next up would be to lean some JS or use HTMX to make the process more smooth.

When washing the dishes at the scouts I cut my hand open on the ladle. That piece of shit has a terrible burr.

@lyse@lyse.isobeef.org Bur I can’t think of what’s changed to cause this? 🧐

What exact feeds are we talking about that uses spaces instead of tabs or the T’s in timestamp?

On a vu The Brutalist hier soir. Je suis très surpris de ne voir aucun commentaire nulle part sur la toute fin du film, la dernière image, presque subliminale. Elle résonne pourtant si fort avec la dernière phrase du film, l’interrogatoire du début, la photo de l’entracte et bien d’autres éléments… Peut-être que je me trompe #cine #film

@prologic@twtxt.net Of course you don’t notice it when yarnd only shows at most the last n messages of a feed. As an example, check out mckinley’s message from 2023-01-09T22:42:37Z. It has “[Scheduled][Scheduled][Scheduled]“… in it. This text in square brackets is repeated numerous times. If you search his feed for closing square bracket followed by an opening square bracket (][) you will find a bunch more of these. It goes without question he never typed that in his feed. My client saves each twt hash I’ve explicitly marked read. A few days ago, I got plenty of apparently years old, yet suddenly unread messages. Each and every single one of them containing this repeated bracketed text thing. The only conclusion is that something messed up the feed again.

@movq@www.uninformativ.de Hahahaha 🤣

@aelaraji@aelaraji.com “replies” 🤣

@lyse@lyse.isobeef.org Duplicates again where two days ago? I don’t see this anywhere (unless I’m blind!)

@lyse@lyse.isobeef.org Agree. I’m not sure we should lax the timestamp format at all IMO. What @xuu@txt.sour.is has found is kind of nuts haha 😆 However I do think we should relax the \t separator between <timestamp> and <content>. Let users use any valid whitespace here that isn’t a newline or carriage return.

I think the author is a bit out of their depth here. A linear feed isn’t quite what the author seems to be modelling in their view of the problems they observe and describe. A linear feed has a beginning and an end. You can (ideally client-side) sort it by Date, or by Subject like we do with our Twtxt clients. A Tree-structure isn’t what the author thinks either, this is more the structure that forms after you introducing some kind of “threading model”. The main problem with any kind of information system that tries to figure out algorithmically what you want to “see” is that type of interface has no start and no end. SO you end up with a “scroll of doom”.

The article discusses the challenges posed by linear social media feeds, which often lead to disengagement and difficulty in prioritizing content from friends due to constant scrolling. The author proposes an alternative approach using a daily feed structure per day, which organizes posts by date, allowing for easier prioritization and reducing mindless scrolling.

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

What exactly is a linear feed? 🤔

@andros@twtxt.andros.dev … I hope they pay you enough for this horrible task. 😂

@movq@www.uninformativ.de Ja, völlig behämmert. Schade, vertane Chance für einen „Doch“-Knopf.

@lyse@lyse.isobeef.org Ja, nein, abbrechen? Wie, was? Was machen Sachen? 😂

En fait, je veux un truc comme autoblog, mais pour n’importe quel site, en pouvant soumettre une url à la main. pour ceux qui ne voient pas, autoblog c’est ça: https://sebsauvage.net/streisand.me/instructions.html (chez <@sebsauvage@framapiaf.org>)

Je recherche un outil qui me permettrait d’obtenir des snapshots de page web, un peu comme le fait archive.org. J’ai le sentiment et l’envie d’archiver pour la postérité, avant la disparition inopinée de ressources de valeur. Vous auriez des conseils? script avec #curl? Truc en #auto-hébergement?

Boah, jetzt mal ernsthaft, was ist denn das für ein Dialog bittesehr!?

Image

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.

@prologic@twtxt.net Tolerant yes, but in the right places. This is just encouraging people to not properly care. The extreme end is HTML where parsers basically accept any input. I’m not a fan of that. Whatever.

@prologic@twtxt.net The issue is that all bracketed text in the entire feed has been duplicated again two days ago. The bug is not fixed. Or it’s a new one.

@movq@www.uninformativ.de I can relate to that. :-/

How it’s going? This is how it’s going: https://movq.de/v/b744b63cc1/oh-fuck-sleep.mp4

Ouiiii, je suis liiiibre, mes corrections sont terminées! 😌

Mes élèves n’imaginent pas l’impact positif de SOAD dans mes oreilles lorsque je corrige…

@aelaraji@aelaraji.com You can update the package 😀

@andros@twtxt.andros.dev My first point of advice is to stop everything and measure all the important critical user journeys. Design and Build Service Level Objectives for each and every part of the system you can find that any user cares about.

2024-08-04T11:24:34Z was the last occurrence of this.

@bender@twtxt.net @lyse@lyse.isobeef.org This bug was fixed back in September last year. But the brackets still appear in my current feed. is that what the issue is? 🤔

@lyse@lyse.isobeef.org @andros@twtxt.andros.dev Are we talking about yarnd here? Hmm? 🤔 I’ve thought about a “read flag” but I just haven’t bothered so far…

@johanbove@johanbove.info And what are the results so far? 🤔

The cache is only suppose to be for 120s though, but I reckon the caching layer is just stupid? 🤔 (and maybe buggy)?

I need to understand how the caching is at play here at the edge. I hit CTRL+R on @mckinley@twtxt.net’s OP to get the right subject reply after poking at the underlying HTML elements on the page.

@bender@twtxt.net To be fair, I do this in my “spare time” 😅

@mckinley@twtxt.net Ahh. I think this is some kind of weird caching issue at my edge! 😱

@mckinley@twtxt.net I’m worried we’re really approaching a point where we need to adapt the hashing algorithm and expand the no. of bits. Is it at all possible something else is going on here though? 🤞

@lyse@lyse.isobeef.org True, but we should also consider building tolerant “systems” 😉

@algorave.dk@algorave.dk Hello 👋

@andros@twtxt.andros.dev it seems your GtS has issues:

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.

@twtxt.andros.dev@twtxt.andros.dev it might be fine, but not here. It just causes more issues than fixes.

@lyse@lyse.isobeef.org not quite. Yes, the feeds on Yarn have episodic messes. But look at mine, and compare it to McKinley’s. It is night and day.

@andros@twtxt.andros.dev I suggest to not touch it and work on a different project instead. :-D

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.

@andros@twtxt.andros.dev I’m all for elegant solutions. I prefer when the computer helps me to really achieve my goal and solve it completely, not where I still have to manually filter a list by hand. Anyway. :-)

@eapl.me@eapl.me Yeah, you need some kind of storage for that. But chances are that there’s already a cache in place. Ideally, the client remembers etags or last modified timestamps in order to reduce unnecessary network traffic when fetching feeds over HTTP(S).

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). ;-)

Have you ever had to refactor a project that was not documented? Any suggestions?

I think it is not easy to implement, you need a database. Timeline is an elegant solution: read and sort.