@prologic@twtxt.net true, but doesn’t need to necessarily. A single user pod is still a pod. Now, Yarn is this, which I use now.
@eapl.me@eapl.me 100% would, but I don’t know PHP. I can help testing, and offering ideas. I read somewhere you want to write a remake, right?
One of the things the current model is missing is templating… I think. Maybe start by abstracting that from the code?
@eapl.me@eapl.me oh, trust me. I know what can be done with PHP.
@aelaraji@aelaraji.com everything’s irie, mon, no worries. :-)
@xuu replying to “hmm.. indeed.”
@xuu hmm.
@xuu thank you! Money withdrawn.
@aelaraji@aelaraji.com that’s much closer, yup.
I don’t think calling the various PHP files making up “Timeline” a “Yarn pod” is accurate.
@prologic@twtxt.net well, stop doing that mate! LOL.
@aelaraji@aelaraji.com icons at the top are badly organised while on mobile. About the speed, that’s using a shoddy PHP code, it would be slow even when running in a quantum computer. :’-D
The hmm… refers to https://aelaraji.com/timeline/conv/7tdi2mq
Cloudy and spotted gentle rains here and there. I think this is the preamble of a cold front (here), which means temperatures will be on the low 20s this weekend and, with any luck, next week. :-D
@eapl.me@eapl.me I think you may have:
Deprecated: Creation of dynamic property Twt::$timestamp is deprecated in /homepages/4/d818294726/htdocs/eapl.me/timeline/libs/twtxt.php on line 443
Kind of issue. :-)
undefined array keys
and creation of dynamic properties being deprecated
(CC: @sorenpeter )
@aelaraji@aelaraji.com the one you mentioned on your twtxt, but it cannot be seeing here (twtxt.net). Even for feed I am not following, twtxt.net will always show the context. There is no context for this reply of yours.
undefined array keys
and creation of dynamic properties being deprecated
(CC: @sorenpeter )
@aelaraji@aelaraji.com I don’t see a twtxt from eapl. What am I missing?
@movq@www.uninformativ.de translating emoji makes it “hopefully nobody pulled that fox up” LOL.
@xuu@txt.sour.is I totally and absolutely blame htmx. 50/50 kidding and serious.
@xuu I figured, yes. I didn’t know if adding noise would help or not. I see, based on IRC comments, that the plot thickens. :-/
@prologic@twtxt.net awfully awesomely brilliant, of course. But don’t take my word for it!
@xuu 67890
@xuu 12345?
@prologic@twtxt.net agreed.
@doesnm@doesnm.p.psf.lt meh, I am not into conspiracy theories, though. I would describe it as rot. I mean, there is still plenty of good stuff, but I am old enough to have taken note on the changes.
@prologic@twtxt.net some good reading about Bluesky, on a similar topic.
@doesnm@doesnm.p.psf.lt I think that, just like a river’s waters (always new, never the same), there is nothing left of KHTML on any browser which was initially based on it. KHTML was a fork of khtmlw
itself, if you want to go down that rabbit hole.
@lyse@lyse.isobeef.org that much, eh? Around how many twtxts?
@prologic@twtxt.net yes, web content indeed is/has become. I will say a little bit of both. Trying my best not to lose faith in humanity. :‘-/
I share my location from my iPhone using “Find My” app with friends and family. I also have a family share, with immediate family.
Even since upgrading to iOS 18, and every once in a while, the location of someone sharing with me gets frozen in time. I see them, but their location doesn’t change for hours. In the case of family share, I can see their device up-to-date, under “Devices”, but they show frozen on the “People” tab. Only way to fix it is for either of us—it doesn’t matter who—to stop sharing, and start sharing again. That has happened to me with three different people, and to three different people, with others (not me).
Is anyone using iOS 18+ experiencing something similar? I have sent feedback to Apple.
Oh my, I missed a test “ajdjeusc” party! Hopefully I can jump on board on the next one. :-D
@prologic@twtxt.net and much faster, and capable. It’s simply an awesome machine.
@prologic@twtxt.net no development activity on that library for two years. Hmm.
@prologic@twtxt.net there is no need to remove them, even more so when others find it useful. I simply answered your query. :-)
@prologic@twtxt.net I forgot the “why not”, sorry. I see, nor have, use for them.
@prologic@twtxt.net I use none. I exclusively use “Discovery”, and “Mentions”, nothing else.
@prologic@twtxt.net one of its key principles:
“Focus on the process: Kaizen emphasises improving the processes that create products or services, rather than just focusing on the end result.”
@prologic@twtxt.net that’s the assignment to end your Sunday. Look it up! :-)
@prologic@twtxt.net a noble aim. Kaizen!
@prologic@twtxt.net LOLing IRL!
@prologic@twtxt.net no, notice the Markdown is broken.
@lyse@lyse.isobeef.org well, boohoo! :-P
Parsing on that URL is broken, @xuu.
@lyse@lyse.isobeef.org I am very skeptical on anything happening on [1st of April](https://en.m.wikipedia.org/wiki/April_Fools’_Day). LOL.
@prologic@twtxt.net I will make it in. Will make sure to tell mum in advance that “I have a meet with the boys”. LOL.
1
Twt from @bender 🥳 Turns out just before I accidentally nuked my pod, I took a dump of it's cached just seconds before 🤣 -- So I was also able to rebuild anything that was missing from the backup from the recent cache dump!
@prologic@twtxt.net time for a well deserved rest. Get well soon. Before you go, monthly call next weekend? If so, set the banner now! :-)
@aelaraji@aelaraji.com oh, you still had an account there? Oh dear.
@aelaraji@aelaraji.com hahahaha! What?! And prive you from framing it with all its magnificent glory? Never! :’-D
@prologic@twtxt.net woot, woot! @lyse@lyse.isobeef.org came to save the day!
@news@twtxt.net all good, and thank you @prologic@twtxt.net for the transparency, and quick action. I feel lighter already! :-D