@darch@neotxt.dk Sounds good 👌
@justamoment@twtxt.net Cool 😆 👌
@jlj@twt.nfld.uk Yup the help feed is gone. Does it still show up for you? 🤔
@akoizumi@kyoko.nerdpol.ovh What’s the problem ?
@carsten@yarn.zn80.net it’s amazing to think that Meta has over 85,000 employees – Or sis have 😅
To further expand (I just re-explored this myself, I guess I’m used ot it? 🤔)
- In Timeline view, a Reply will show the (#hash) you’re replying to.
- In Conversation view, a Reply _will not__ show the (#hash) you’re replying to. It’s implied from the Conversation view.
- In Conversation view, a Fork will show the (#hash) of the Twt you’re replying to and forking.
I guess there’s some subtle differences that we need to take care of in the UI/UX to make things a bit more obvious and clear before we go completely hide them from the interface? 🤔
@axodys@octobloc.xyz Well there is nothing to work-around per se, just ignore it for now. But yeah in general we’re trying to remove the (#xxxxxxx) hash from the text area when replying and forking because we also shove it into a hidden field anyway, so we know what we’re doing generally from the UI/UX and Backend. If you happen to have any Go experience we’d love some help here to finish this work 👌
@carsten@yarn.zn80.net I think this time I will follow suite too and do the same 👌
Oh! That actually sounds interesting 👌
@carsten@yarn.zn80.net I don’t think so. I might hold off on this update.
@axodys@octobloc.xyz yeah, I think it is a bug, or more accurately. I think we only half completed the user and to device change there. 🤦♂️
@axodys@octobloc.xyz they actually both do under the scenes but we’ve been trying to transition the user interface away from explicitly showing what happens and I think we’re only half did it 😆
@justamoment@twtxt.net Oooh that’s a good point and great question! Should we have an option to exclude from your main timeline view when you add a feed to a list? 🤔
Yeah I saw a few projects like that 👌
@mckinley@twtxt.net LOL 😅
as I often have my iPhone directly underneath my iMac. Yes, I completely agree with you that feature is going to completely piss me off! 🤦♂️
@axodys@octobloc.xyz What’s it about? 🤔
macOS Ventura - Apple (AU) – Anyone on macOS Ventura yet? Any problems you’ve run into? What new things do you like? 🤔
honk
here will it show up on mastodon?
@abucci@anthony.buc.ci I gathered that 🤣
@tkanos@twtxt.net I think we already actively are… But please do keep contributing those suggestions, ideas, etc. And I welcome your PR(s) too as I need all the help I can get 🤗
honk
here will it show up on mastodon?
@abucci@anthony.buc.ci “Hong”?! wtf is that?! 😅
@mckinley@twtxt.net Haha 😅
I think I’ve seen this before and even tried to study its source code and got “turned off” by the fact is wants to tie everything to a freak’n database 🤦♂️
@tkanos@twtxt.net Why’s that? Is it just the people that are on Mastodon that’s the issue, or how Mastodon works (or doesn’t) work? 🤔
Interestingly there’s more things about Brazil that our search engine is able to find that I expected 😅
@mckinley@twtxt.net Now do one on Twtxt vs. Activity Pub and then Mastodon vs. Yarn.social 😅
@mckinley@twtxt.net Yeah that would work too as an alternative. More build work though… Also I already have Plex (paid for a lifetime license some years ago). I’d have to make sure (if I continued to use Plex on the move) that it didn’t require outside network access just to function of course (which would be silly) 😅 – Only other thing to solve (if I went down the RPi + something route) is audio/music streaming… Need a way to stream to essentially a set of speakers that seem to only have an FM receiver hooked up to them, but maybe there’s an audio jack somewhere hmmmm 🤔
@mckinley@twtxt.net That’s a good thing right? 😅 – And… Hence the driver for better filters? 🤔
@eaplmx@twtxt.net Yeah 😅 I found something that may solve one part of this:
I’ll fork this myself 😅 – So far I know of Western Digital My Passport Wireless Pro | Plex Support which will let me take a portable “Plex Server” on the move with me and copy a subset of our media (TV Shows, Movies, Music) on the portable drive which runs a Plex Server and builtin WIFI Hotspot.
Problem is, this is only good for connecting say iPad(s) or iPhone(s) to the hotspot and using the Plex App. I can see no way to then stream something to a portable 12DC powered TV that basically only has HDMI input (and some older shit)…
I need something to connect to a wifi hotspot, stream a plex stream and re-stream that to a HDMI input source 🤔
I don’t want to derail this Yarn, so please fork this when you see it 😅 – Speaking of FM Transmitters and what not, I actually have a new project I’d like to build with two requirements:
- Some kind of small compute device that can be powered either via USB or 12V DC Socket
- A built-in FM transmitter so I can stream a subset of our own music (we’d copy form our NAS initially).
- A way to stream Plex into the HDMI input of a small portable TV screen (also powered by 12DC)
Fortunately when I type the @
(or use the button) that feed no longer auto-completes for me… So that’s good. @darch@neotxt.dk maybe is still following it maybe? 🤔
@eaplmx@twtxt.net Maybe let’s leave it for now… Maybe you could help me figure out how to actually deal with “dead feeds” and “premaritally gone” in some sane way?
@eaplmx@twtxt.net Bahahaha 🤣
Looks like I was still following that feed myself. Now I’m not… And it looks like it still returns just fine, so its still possible to pull it into pod cache’s and have a Twter
object for it… Hmmm…
@eaplmx@twtxt.net The “Twter” object is probably still in @darch@neotxt.dk’s pod’s cache… Do you know what the URI of that feed was? Does it now 404 or NXDOMAIN or something else? There is a real problem with yarnd
’s cache in that whilst we track “dead feeds” and “moved feeds” we don’t handle cleanup every well (yet…) – Working on it…
@coys@octobloc.xyz Are you basically at a game and posting the game in play? 😅
@batyshkaLenin@alexandr-sidorenko.me So does this mean you can finally reply to others in your client? 😅 🤔 (not sure if you follow me though…)
Or in the case of Mastodon – Too complicated to stand up. And ActivityPub, too hard to build against. So I (almost by accident, I was looking…) came across the Twtxt spec/format and voila 👌
@eaplmx@twtxt.net Yeah well the rest of the back story is documented at About Yarn.social 😅 I realised I actually did want some kind of micro-blogging / social media “thing”, but I hated Twitter™ (had an account once upon a time, deleted, re-created, deleted, and finally deleted and never used it), and any other social media are basically “yuck”, advertising centralised piles of garbage 😅
@eaplmx@twtxt.net Remove it from where? 🤔
@coys@octobloc.xyz Hey! 👋 Welcome! 🤗
@darch@neotxt.dk I will try your idea of using an “aside” element here, but for now I’ll just use the same idea of links/buttons with just a different colour for “include”, “exclude” and “off”.
@eaplmx@twtxt.net Even though I don’t use Pinterest and never “got it”, I do see some value in its “features”. Speaking of which… I believe @darch@neotxt.dk @hashrock@twtxt.net and I think even my dad @off_grid_living@twtxt.net would want and benefit some some kind of visual sharing UX on Yarn… I would fully support this (somehow), question is how… I’ve always thought we would just surface “media” as search results, but @hashrock@twtxt.net seems to think we can also have a “portfolio” profile view of some kind… Maybe some combination of both? I dunno 🤷♂️
@axodys@octobloc.xyz Hmmm? Like this? 😆
@abucci@anthony.buc.ci Nope not at all. Yarn.social was born out of a desire to be able to conveniently “blog” without the burden of a full blog which is time consuming and someyhing I never managed to do very well/
@darch@neotxt.dk I could give that a go.
@justamoment@twtxt.net The main drivers behind lists are a couple of basic needs. @abucci@anthony.buc.ci for example would want to categorise some of his feeds as “fast” and others as “slow” and have different views for those. I would want to categorise some favourite web comics as “comics” so I don’t miss them (currently I missed them because they are inconveniently posted at the wrong times). More background/history can be found in the issue