This is one simple way of making #filters work: FeedLand’s feed list is also a feed reader. - YouTube
@prologic@twtxt.net So each user on a pod would no even be able to the list of who follows them? Or is it just the counter you want to get rid of? And both for Followers and Following?
@prologic@twtxt.net a what?
@prologic@twtxt.net yes that is about right
@prologic@twtxt.net Not but it seem to be good enough for this😆
External and selfhosted feed:
Feed on an external pod:
Feed on local pod:
Hmm I need to work our the logic for the last one for internal users to not show the link to home pod
@eaplmx@twtxt.net gracias namnam
@prologic@twtxt.net I think i found a hack:
{{ if not (eq $.Profile.NFollowers 0) }}
@prologic@twtxt.net fair enough. I will find a way to design around it then
@prologic@twtxt.net so you don’t think we can test for it in any way? Like there are some backend communication happening between pods, right?
@prologic@twtxt.net I need to filter out profiles or feeds that are not on any pod, but selfhosted like with lyse, movq and my own at http://darch.dk/twtxt.txt, since these does not have a rss/atom feed (https://neotxt.dk/user/darch/atom.xml) or a profile page (https://neotxt.dk/user/darch) and it therefor makes no sense to show links pointing to 404
@prologic@twtxt.net and that will not just give me internal users instead?
@prologic@twtxt.net I could use some help in figuring out how to only show the homepod and RSS link if it is actually there. Is there as way to know in yarnd if the feed is on an another pod or if it is self hosted and does not have RSS or profile page?
Now with Logout move to your profile page, which can then be easily accessed from the topnav:
And a CSS-only modal for the Mute/report feature:
Some more work on the new profile_ui:
Yes that make sense in regard to indirection.
@prologic@twtxt.net to work as a bridge the the indieweb world. What do you mean by indirection?
Could feeds.twtxt.net be setup to send Webmention to the original site when replying to a post?
ttis just a frontend. And would like to be able to use it one day
@prologic@twtxt.net because TT looks cool on the screenshot with the nested threads. But tbh i never gotten around to try out any CLI/TUI clients beside the original one by buckket
new #logo for yarn.social
https://sfsf.shop/answerswithjoe/ and https://thefutureisrad.creator-spring.com/listing/sfsf20-009?pr=ANSWERSJOE
@abucci@anthony.buc.ci agree so much with these problems. When it looks like an e-mail, but is not, that will confuse the hell out of most people compared to a (sub.)domain syntax.
@<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch 😅
It is not all twtxt.txt file that adhere to having a nick = or url = field int them, so the only information we can be sure of is a URL to where the twtxt.txt is served from. That leads to using a domain+path-to-twtxt.txt as be most unambiguous identification and also how the original @<URL> mention are defined in line with the indieweb way of using a domain as id.
But with muti-user pods this get messing with urls like https://neotxt.dk/user/darch/twtxt.net, when it would be much nicer if we had http://darch.neotxt.dk/twtxt.txt like on https://darch.neocities.org/twtxt.txt and then we could omit the /twtxt.txt in daily conversation. </ramble>
but I do get that you want to build something better
@lyse@lyse.isobeef.org I like the idea that you are still using the original client as a backend and ttis just a frontend. And would like to be able to use it one day
@lyse@lyse.isobeef.org I’m no longer using my account on twtxt.net, so no real need to still follow it.
I just keep it around to preserve the history and if I ever need to log in and test something on twtxt.net.
@lyse@lyse.isobeef.org yes to what @prologic@twtxt.net said
New profile_ui is slowing coming together:
"nick": field in the JSON
@prologic@twtxt.net yes and leaving out the nicks which you can also not really edit when they are saved to to yarnd following list. You need to delete and re-add them. But if we get around to building something like this http://darch.dk/yarn/lists-mockup-01.html then it would be easier to fix
"nick": field in the JSON
@prologic@twtxt.net My point was also that the client should match and replace @prologic with @<https://twtxt.net/user/prologic/twtxt.txt> and prompt the use in some way if there are more than one prologic like yarnd already does with the popup and autofill.
"nick": field in the JSON
@prologic@twtxt.net so anyway people should start using the longform mentions of @nick@url and not just @nick and the the client (yarnd) need to verify it and convert it to the proper mentions. Maybe even just as @<source.url> over @<source.nick> to omitting the spreading of bad nicks. (Ref: twtxt file — twtxt 1.3.2-dev documentation )
@prologic@twtxt.net I only had MacBooks where it a reasonable feature to put the computer to sleep to conserve battery
@prologic@twtxt.net I’m still on MacOS 11, but can you still use apps such as Caffeine?
@prologic@twtxt.net cool, so can this be used to improve the data quality of various nicks on each pod? I don’t see a "nick": field in the JSON
@prologic@twtxt.net no but we could make some recommendations for how clients are to deal with issues like this
@prologic@twtxt.net yarnd simply does not understand markdown tables, i guess it not included in the parser.
@lyse@lyse.isobeef.org any idea how to fix this accoss pods and self hosted twtxt files?
@lyse@lyse.isobeef.org you mention here looks wierd
@prologic@twtxt.net I’m on Old Zealand but we still got 9.5h left of 2022
Also if you go to the link you can see that I added a RSS/atom feed as well, which i believe used to be there back in the days
@justamoment@twtxt.net yes this exactly the idea with the [text in brackets] 😉
Mockup for redesign of the profile page https://wireframe.cc/XvxNVE
@justamoment@twtxt.net that’s great and the horizontal scroll should first kick in below 740px, above that the filters simply do a line wrap as before. But I guess you already know that after trawling thought the code😉
There is a PR waiting to be merge now fixing the overflow causing horizontal scroll on mobile
It includes the horizontal scroll for filters on mobile, but it commented out in the CSS for the time being.
@prologic@twtxt.net also: mobile - Filters in a horizontal scroll or in a dropdown; what is better? (i made an example image) - User Experience Stack Exchange
@prologic@twtxt.net so you just want a dropdown instead of a horizontal scroll? I’m not gonna do it this year, since I believe what we have now is sufficient. At least until we got lists up and running as I posted about earlier today: https://neotxt.dk/twt/vef7xva
@prologic@twtxt.net so it is the dropdown feature that you like?!
Sure we can do that, but then the user have to type out what they want and it don’t see that as very mobile friendly…
or do you mean the filters in the side menu?
@prologic@twtxt.net ah okay, so just like using site: or date: in any mainstream search engine. Why do you bring this up here?
@prologic@twtxt.net nope, do you mean topics like https://github.com/topics/twtxt ?