@lyse@lyse.isobeef.org Hmmm 🧐
@prologic@twtxt.net That boycott didn’t last very long, eh!?
Yeah, sounds like another hype train arriving at the station.
tt
rewrite in Go and quickly implemented a stack widget for tview. The builtin Pages is similar but way too complicated for my use case. I would have to specify a mandatory name and some additional options for each page. Also, it allows me to randomly jump around between pages using names, but only gives me direct access the first, however, not the last page. Weird. I don't wanna remember names. All I really need is a classic stack. You open a new fullscreen dialog and maybe another one on top of that. Closing the upper most brings you back to the previous one and so on.
@doesnm@doesnm.p.psf.lt I’ll let you know once it reaches a point where it might be barely usable by someone else than myself. There are long ways to go, though. Right now, you don’t wanna even look at it. :-)
@movq@www.uninformativ.de fuck 🤣
@prologic@twtxt.net One of my coworkers cats is officially named “piss cat”. 😂
robots.txt
that I have on https://git.mills.io/robots.txt with content:
* 185325d - (HEAD -> master) edge: Ban Alibaba (38 seconds ago) <James Mills>
fark me 🤦♂️ Alibaba, CN has been hitting my Gopher proxy quite hard as well. Fuck’n hell! 🔥
robots.txt
that I have on https://git.mills.io/robots.txt with content:
* 8a77b64 - (HEAD -> master) edge: Ban Google's ASN (21 seconds ago) <James Mills>
It would appear that Google’s web crawlers are ignoring the robots.txt
that I have on https://git.mills.io/robots.txt with content:
User-agent: *
Disallow: /
Evidence attached (see screenshots):
– I think its the the Small Web community band together and file a class action suit(s) against Microsoft.com Google.com and any other assholes out there (OpenAI?) that violate our rights and ignore requests to be “polite” on the web. Thoughts? 💭
I got promoted today to try using Passkeys on Github.com. Fine 😅 I did that, but I discovered that when you use your Passkey to login, Chrome prompts you for your device’s password (i.e: The password you use to login to your macOS Desktop). Is that intentional? Kind of defeats the point no? I mean sure, now there’s no Password being transmitted, stored or presented to Github.com but still, all an attacker has to do is somehow be on my device and know my login password to my device right? Is that better or worse? 🤔
Our stupid fucking 🤬 cat 🐱 keeps pissing 🚽 everywhere in our house 🏠
I’m continuing my tt
rewrite in Go and quickly implemented a stack widget for tview. The builtin Pages is similar but way too complicated for my use case. I would have to specify a mandatory name and some additional options for each page. Also, it allows me to randomly jump around between pages using names, but only gives me direct access the first, however, not the last page. Weird. I don’t wanna remember names. All I really need is a classic stack. You open a new fullscreen dialog and maybe another one on top of that. Closing the upper most brings you back to the previous one and so on.
The very first dialog I added is viewing the raw message text. Unlike in @arne@uplegger.eu’s TwtxtReader, I’m not able to include the original timestamp, though. I don’t have it in its original form in the database. :-/
Next up is a URL view.
@movq@www.uninformativ.de That’s what I immediately thought as well. :-D @eapl.me@eapl.me Unfortunately, no fancy buttons. What does your model do?
@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
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?
@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 🤣
@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:
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.
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.
Mastodon Experience: The author’s experience with Mastodon highlighted its effectiveness in allowing content prioritization and managing social media usage without dependency on algorithms.
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.
- Implementation Challenges: Creating a daily feed system involves organizing content effectively and ensuring users can prioritize posts.
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.
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? 🤔
@eapl.me@eapl.me I like this idea. Another option would be to show a limited number of posts, with an option to see the omitted ones by user. Either way, I wonder how well that works with threading.
@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? 😂
Boah, jetzt mal ernsthaft, was ist denn das für ein Dialog bittesehr!?
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.
Now I just have to remember to tag people in replays ✍
… And, HOLLY!! infinite scrolling is real!! 👀
@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
I just did and things are working wonderfully well now and I’m in love with how profile views
are layed out! 👌 Thank you!
@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.
@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! 😱