273
results for "sorting"
-
This was based on sorting by date primarily, and having very variable in links.
[KevinMarks]
at
2023-04-01 19:15
-
Update from me: I know things have been continually stagnant. I'm in the process of a final house move after literally eighteen months of upheaval. I plan to spend a lot more time sorting Known out and finally finally getting a stable release out.
[benatwork]
at
2023-02-10 16:49
-
Also thanks for the great talk James, was quite informative, and gave me the nudge to finally see about sorting out webmentions on my site :)
yousef
at
2023-01-15 19:11
-
ok, I added "a new interface experiment for Mastodon, with the idea of reading based on person rather than time-line or sorting algorithm. https://fasiha.github.io/yoyogi/about" to the "See Also" section of /reader https://indieweb.org/wiki/index.php?diff=84908&oldid=79774
Loqi
at
2022-12-05 04:52
-
reader << a new interface experiment for Mastodon, with the idea of reading based on person rather than time-line or sorting algorithm. https://fasiha.github.io/yoyogi/about
[eddie]
at
2022-12-05 04:52
-
reverse chronological sorting is literally a sorting algorithm
aaronpk
at
2022-11-30 17:20
-
I’d be up for adding a function to mf-cleaner which removes any microformats with these false-positive root classnames from the tree, re-sorting any children back into place
barnaby
at
2022-11-14 21:40
-
hmm okay so in that case, I’ll go with having an ISO8601 exact datetime for sorting, and then separate local YYYY, MM, DD and slug columns for use in URLs
barnaby
at
2022-10-30 19:53
-
aaronpk: I’m leaning toward having separate columns for local datetime (without timezone, used for URLs) and ISO8601 timezone for sorting
barnaby
at
2022-10-30 19:41
-
but another approach is thresholding - if you fetch both already-known and "remote" venues, sorting them by whatever is closest will probably always make sense, as long as location accuracy and density are good.
[schmarty]
at
2022-10-24 16:32