Lack of attention to details is one of my pet peeves. Thank you for doing this!
Spent an unusually long amount of time normalizing the underlines in this site to be consistent everywhere.
Better don’t ask, just fastidious.
If I click on this one from "Latest", the link is: /post/1144?from=%2Flatest%23post-1144
, what the rationale behind the change on link and permalinks to notes, and tags, etc.?
That's a novel approach, , thanks! I also saw you tweaked the interface, so now it looks *very* good on mobile. Thanks again!
Your wishes have come true (well, almost) - you can now search for handles and hashtags while you are writing a note/reply - it will preserve what you've written so far and you can find what you're looking for!
Err, (not having autocomplete, I am surprised I haven’t made this mistake before!)
Please pass this to your developer, @stafas. ☺️
Please pass this to your developer, @stafas. ☺️
The mobile UI needs some work still. Much better than before, but not cigar. Writing a new post, or reply zoom it disproportionally, and the “hot”, “for you” are all piled up. Same for following, follows, etc.
The mobile UI needs some work still. Much better than before, but not cigar. Writing a new post, or reply zoom it disproportionally, and the “hot”, “for you” are all piled up. Same for following, follows, etc.
Noticing how very few
fix:commits we have in the textlog repo. Codex is a much better developer than me. I'm now a project manager I guess.
Oh, no, no, I never implied, nor intended my report to be actionable by !
I'm sure will fix it eventually, I'm not in control of the app.
Just tried logged in, using web, still the same, no Markdown rendering (looking at inline/block codes only). It doesn’t render LaTeX either.
Darn. or.. .
Of course I did. That's how I know it isn't working. :-D
Did you enable it from the settings? It's off by default.
Render Markdown isn't working (I am not logged in) while using the web version of the app (the only version I have played with).
Big release for the flutter app. Writes are now native! Frontend post filters, account details, etc. Eager to hear what you guys think to iron out inevitable quirks.
It sure is a feat! Now isn’t TypeScript essentially JavaScript? 😅
Can you believe the amount of 's and nuance in this site and we're still zero (well the core at least, apart from the notifications). I can't.
Saw it, and loved it! I was about to propose it, as the mobile app has it. It is especially useful for when a thread goes long, to go back where it started.
If you haven't seen them, there are now
backlinks in post and reply pages, making it easy to jump to your previous location, without using the browser's back button which sometimes has issues (after submitting forms etc.).
Indeed, that's a good use case. I mean, I am just not *that* interesting. :-D
They're useful for tracking a thread of posts e.g /tag/feature
Aha! That's great. I will never hit the wall, I use none. :-D
#five, #no #more
We haven't seeing an issue yet, right. I think limiting the amount of hashtags per post would be a good thing to implement *when*, and *if*, becomes an issue.
What do you mean? Once a tag isn't used it's buried away to the last pages. Why worry about it?
I have found engaging with people in other languages to be an advantage. There are translators in all platforms!
Are there any plans to filter by language? What will happen when people start posting in several languages?
Each time something similar has happened to me, I have checked the repo and, sure enough, have seeing changes that merit an application restart. 😅
I tried to post a reply but something happened and it got lost. Maybe server refresh? Had to re-type it :)
If you didn’t mention it, I wouldn’t have realised there was a way to collapse threads. Pretty cool!
Implemented.
Ah, then it isn't , it is . :-P
Unfortunately no. Just starting it. Got the proof of concept loading a dir with its sub-dirs then rendering on the GPU in textures silky smooth. 1.7mb executable, but will need to level up to SDL and that will double the size I think.
Minimalise! You got my vote (and my axe!).
Should we consolidate /for-you and /activity ? Basically get rid of
activityand just put all infor you? Now the semantic difference isactivityyou can scan for direct interactions with you, wherefor youhas also random public posts.