Tucson Coyote™@dielan Was part of my inspiration for #dopebox
.
“How hard would it be to write a mastodon client? I don’t really like Amaroq works.”
Anyway, if you do that, which I think would be cool, I’m using Amoroq on iOS and see issues…
One thing I seem to dislike about all apps and front ends is link rendering, which I think should be in place, and handle links to fedi posts different than normal URLS (not spawn external browser/window/whatever).
And, if you want to expand the thinking beyond a twitter clone, the way #DopeBox or Lemmy looks at content in ‘other than timeline’ ways would be way cool.
Dude, my concept (no code at all yet) needs a developer.. LOL. Follow #DopeBox and last line in my profile. More than happy to have anyone work on that in any way at all… I’m blocked behind dialup speed right now for a week or two, and got a day job finally that’s taking up all my time, and I can’t code my way out of a wet paper bag anyway…
@PawelK Yea, I’m more interested in the other side, I think, I want more of a barebones, clean database (or even flat file) interface to activity-pub, because every node development project I’ve been looking at seems like so much effort to clone stuff that exists, and none of it is stuff I care about. And the stuff I want to screw around with is buried… I’m more interested in the organization of the data in non-timeline ways (logic trees, reddit styles like lemmy, and eventually back to my #DopeBox idea. But I’m so lost in the complexities of the UI garbage that I don’t care about to really want to dig into any project, yet, but maybe.. I don’t now. I’m probably just dreaming, but I’d think “F’ even having a WebUI, gimme a command line UI that can be a building block for lots of fun other UI implementations, like apps… But, what do I know…
We could bring back gopher on VMS servers that run fedi nodes, the OS that was designed to use FileSystem-11 that structures the filesystem TO be distributed on nodes, since the beginning.
This is a test, this is only a test, of the URL rendering in posts I am using to view from different FEs to see which URL is rendered when multiple are used.
Ideally, you would see this url as a preview, in place: https://join.misskey.page/en/
And then, another URL, below this line of text, rendered in place: https://spinster.xyz/
And even a third, fourth, fifth, rendered in place, wherein, if it’s a link to an off-node fedi post, it just switches you to that thread when you click on it, not spawns the browser opening an unconnected page where you can’t comment: https://shitposter.club/notice/A4wPPNtOl9v2FXfs12
So that you can navigate the Fediverse faster using #DopeBox (when I figure out if I’m going to get around to actually STARTING this thing). https://en.wikipedia.org/wiki/Fediverse
Soapbox exploration note for #DopeBox: soapbox-fe/app/soapbox/features/status/components/card.js autoplay probably needs to be “off” for #DopeBox, because if it’s previewing multiple URLs, all playing at once would be fuxed.
Now, is “card.js” called somewhere… am I actually even looking at the “how to build the display of the contents of a status/post/note (inconsistent terminology across FE projects I guess?)?
@PawelK this is part of the frusturation I wish I could solve with #DopeBox, I put in a link, but rather than it seeing it was a fedi link you could follow and just pulling you to a new thread, it opens up a new tab on another node. FML. Anyway, that’s for another day, for now, looking at the Misskey side:
“F me and my ADHD, now I’m reading this shit after trying to figure out what line 75 in note-detailed.vue in MissKey is doing. Somewhere in here I just have to find a FE that I can figure out how to loop the URL rendering… But my ability to focus tonight is all over the map.”
and @defango found it’s got to loop through all urls, rendering in place rather than end of note text, calling url-preview.vue.
I’ve not spotted those calls, but it should probably do it on it’s own special page, not on everything, where ever it is that it’s generating the previews, so it’d be a cp of a page that generates the best previews, hacked to loop through all the URLs in place.