@lyse@lyse.isobeef.org Das ertragā ich wahrscheinlich nur auf Mute. ScheiĆ LƤrm. š¤£
Note to self: If you turn something off, this means it is not on.
tt. I run into this bug almost daily for weeks now.
@lyse@lyse.isobeef.org Ahh ok! I was just wondering and curious whether it was a bug that Iāve caused anywhere along the way š§
set -o multiline.
@dce@hashnix.club I see, ta!
@movq@www.uninformativ.de @prologic@twtxt.net @itsericwoodward@itsericwoodward.com Let me join the Enterprise Ruined It For Me Club. :-D
@david@daiwei.me Yeah, with the long and thus taller list entries, things are getting off hands. Ah, when focused, you wouldnāt differentiate between read or unread.
tt. I run into this bug almost daily for weeks now.
@prologic@twtxt.net A screenshot wonāt help in this case, as you donāt see anything. :-D It starts off just fine with a conversation tree like that:
Unknown conversation root
āā“Read reply
āā“Read subreply
Everything works. After reloading the feeds, a new message becomes part of the conversation, so the conversation e.g. looks:
Unknown conversation root
āā“Read reply
āā“Read subreply
āā“Unread subreply
However, the bug is that the whole conversation is not shown at all. None of the three (or four with the root) messages appear in the message tree view. My recursive SQL determining the messages to display is clearly broken.
Tops 25°C is a very welcome change. Tomorrow just 21°C (but right before I went to bed they forecasted two degrees less today).
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
and @david@daiwei.me your rename shipped š itās āGenerate recovery codeā now (you were right ā mints a fresh one each press), + it asks before replacing an existing code so you donāt nuke the one you saved š
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
quick correction on that cleanup timing š itās not 28 days. nothing gets deleted for the first 30 days at all (observe-only), and after that only setups unused for ~6 months that also never saved a recovery code. saved a code = safe forever š
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
@david@daiwei.me Good point ! š
@david@daiwei.me Nice! š
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
IMPORTANT: Treat the re oery code like a password.
twtd instnace or via Github/Gitea or any other publishing backend (doesn't amtter). Please read.
I will be monitoring the server logs for the next ~28 days, after that orphaned Namespaces will start to get cleaned up, especially ones that have never bothered to care about recovery.
š£ ACTION REQUIRED: Hey folks š For those of you whom are using the Twtxt App either via the Hosted option or on your own twtd instnace or via Github/Gitea or any other publishing backend (doesnāt amtter). Please read.
Please open the app and you should be prompted to save your recovery code for your device. This basically is all of your settings, follows, etc in the app itself. This is synced to the Origin everytime you make a change, and also stored on-device. This is what makes it possible to sync your setting across services, move to another device, etc.
Please save a copy of the recovery code somewhere. This is only your only way to recover your settings.
Thank you š
Posting the review and plan here for posterity as it is related to this thread: https://canvas.mills.io/a/6QVGjzRW
The PR(s) as-is will likely not go ahead Iām afraid. More work to be done, but this is basically all about the āRecoveryā story and how to anchor and notion of an āaccountā without well umm an account š¤£
@david@daiwei.me Ma too š¤£
@ponderpoints@twtpub.com Welcome to Yarn.social š Interesting video, I actually watched it all the way through, riverting stuff really and quite well put together. The idea of āsubjective experienceā is a rather complicated thing to describe and youāre right, how do we even know we have them? š¤
@david@daiwei.me Holy moly š±
Ahh yes! Please do upgrade your twtd instance. Few things changed, many bugs fixed there too.
@balloon-fu-sen@tw.fus.f5.si Huh? š§ This hasnāt changed. What has is the default proxy used depending on your publishing backend.
@david@daiwei.me Itās truly mind-boggling. All the hand full of episodes Iāve seen so far on this channel are amazing. Totally worth tuning in. I have to catch up a lot. :-)
SpitzenmƤĆige Doku über @movq@www.uninformativ.des kleinen Hausflugplatz: https://www.youtube.com/watch?v=F72t2fpiWPo
Thatās such a cool The Rest Is Science episode: What Are The Odds Youāll Become A Fossil? https://www.youtube.com/watch?v=cYvDaDb_mbw
@david@daiwei.me Danke š
@david@daiwei.me Cool š
@david@daiwei.me Please š
Iāll see if I can unblock just that VPN provider š¤
Testing the NEW Composer Preview
@lyse@lyse.isobeef.org Stimmt, das hatte ich vƶllig vergessen. Gab da mal diese Zeit, in der āForenbeitrƤgeā die Pest waren. š¤ Da ist sie also wieder, die rosarote Nostalgiebrille. š
there us a recovery path
no, not what um dating at all
sue expand ed on the main thread
the only reason twtd has and records a followers.json is because thatās where your feed is hosted from and where the UA discover occurs
the correct fix for what you observed is a recovery token to re-sync settings from the sync API
itās client sue not on any publishing backend
not stored on twtd no
@prologic@twtxt.net that are included, part of the first round. LOL.
@bender@twtxt.net I meant the hookers š¤£
@prologic@twtxt.net I will pay for the first round. After that you are on your own! I am Bender, not your dad, right? š
@bender@twtxt.net Whoās buying? š¤
@prologic@twtxt.net well, thank you my good friend! Now, lets go for blackjack and hookers! š
I see you š
Another post, to show @prologic@twtxt.net I am around. I am not dead! Not for 9 days!
@kiwu@twtxt.net ba bį»n nÄm sĆ”u to you, too! š
@prologic@twtxt.net @itsericwoodward@itsericwoodward.com āEnterpriseā Java ruins everything, eh? š I only did that very briefly, luckily.
tt. I run into this bug almost daily for weeks now.
@lyse@lyse.isobeef.org Can you explain this like iām five? 𤣠Scgeenshot?
I should really fix this damn bug where new replies to read replies to unknown conversation roots are not showing up in tt. I run into this bug almost daily for weeks now.
@movq@www.uninformativ.de Ich war nie im Ubuntuusersforum unterwegs. Aber zu Delphizeiten damals im āPlanet Quellcodesā-Forum aktiv, das es lƤngst nicht mehr gibt. Ich schƤtze, die Hochzeiten der Foren sind einfach rum. Heutzutage ist einmal sehr viel mehr Wissen andersweitig zugƤnglich und dann sind vermutlich die allermeisten Leute auch einfach auf Soziale-Medien-Plattformen unterwegs. Oder werden die eigenen Projekte auf dem eigenen Blog und dergleichen vorgestellt.
Dann gabās auch (zumindest gefühlt) eine Zeit, in der man einfach keine sinnvollen Antworten mehr in Foren bekam. So kam das mir jedenfalls vor. Ist schon eine ganze Weile her, aber ich kann mich noch dunkel erinnern, dass ich bei Forensuchtreffern hƤufig auf Reaktionen Ć la āsuch doch selberā stieĆ. Oder einfach zuhauf komplett falsche Antworten vorgeschlagen wurden. Ich hab mir dann angewƶhnt, ForenbeitrƤge komplett zu ignorieren.
Einige Foren haben auch noch damit angefangen, anonyme Zugriffe zu unterbinden oder zumindest einzuschränken. Das half im Rückblick natürlich auch nicht, dieses Medium attraktiv zu machen.
@aelaraji@aelaraji.com Thatās totally fine if you work at the beach. :-)