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 ?

ā¤‹ Read More

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.

ā¤‹ Read More
In-reply-to » i made a little twtxt feed fixer for when a feed uses other whitespace instead of tabs.

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

ā¤‹ Read More

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

ā¤‹ Read More
In-reply-to » @lyse Where? šŸ§

@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.

ā¤‹ Read More
In-reply-to » i made a little twtxt feed fixer for when a feed uses other whitespace instead of tabs.

@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.

ā¤‹ Read More
In-reply-to » Linear feeds are a dark pattern - A proposal for Mastodon https://tilde.town/~dzwdz/blog/feeds.html

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ā€.

ā¤‹ Read More
In-reply-to » Linear feeds are a dark pattern - A proposal for Mastodon https://tilde.town/~dzwdz/blog/feeds.html

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

ā¤‹ Read More

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?

ā¤‹ Read More

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.

ā¤‹ Read More
In-reply-to » i made a little twtxt feed fixer for when a feed uses other whitespace instead of tabs.

@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.

ā¤‹ Read More

Mes Ć©lĆØves nā€™imaginent pas lā€™impact positif de SOAD dans mes oreilles lorsque je corrigeā€¦

ā¤‹ Read More
In-reply-to » Have you ever had to refactor a project that was not documented? Any suggestions?

@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.

ā¤‹ Read More
In-reply-to » Definitely something going on with replies. This one was replying to the wrong twt and even when I got clever and pasted the right hash it didn't work.

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

ā¤‹ Read More
In-reply-to » Definitely something going on with replies. This one was replying to the wrong twt and even when I got clever and pasted the right hash it didn't work.

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.

ā¤‹ Read More
In-reply-to » @lyse As far as I know, they're still visible in the Web UI. Although, in the mobile app and youtube.com, I believe it tells you that the video isn't available without having to click on it. They don't tell you that in the RSS feed, and I agree; it gets annoying.

@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? šŸ¤ž

ā¤‹ Read More

@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.

ā¤‹ Read More
In-reply-to » Have you ever had to refactor a project that was not documented? Any suggestions?

@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.

ā¤‹ Read More
In-reply-to » I think it is not easy to implement, you need a database. Timeline is an elegant solution: read and sort.

@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. :-)

ā¤‹ Read More
In-reply-to » @eapl.me Read flags are so simple, yet powerful in my opinion. I really don't understand why this is not a thing in most twtxt clients. It's completely natural in e-mail programs and feed readers, but it hasn't made the jump over to this domain.

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

ā¤‹ Read More
In-reply-to » Linear feeds are a dark pattern - A proposal for Mastodon https://tilde.town/~dzwdz/blog/feeds.html

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

ā¤‹ Read More