#dev 2023-04-02

2023-04-02 UTC
IWSlackGateway and [schmarty] joined the channel
#
[schmarty]
sknebel: good call on the summary/details for TWITIWAE posts not coming through. Separate from any mf2 proposals I am happy to field alternate ideas for handling these. I really wish audio elements supported vtt tracks. :/
sebbu, geoffo and [tantek] joined the channel
#
GWG
This seems like a problem that needs to be solved, but a mess of proposals that are about the same basic idea.
#
Loqi
[preview] [prof-milki] #44 "extensions": ["…"] extension / registry
sebbu and [marksuth] joined the channel
#
GWG
Following up, is that a bad thought?
[jeremycherfas] and chenghiz_ joined the channel
#
bkil
capjamesg: The first alternative is if your domain name is short enough and your linking scheme is also terse and fluid, you might want to just include the full external link under its own named section and link to _that_ anchor in the printout. E.g., my.example/2023/04/short-url#9
#
bkil
The second is to create a dedicated section on your website and indeed implement a sort of link shortening where you create one internal page (or anchor) for each external URL. For best future proofing, I recommend reusing some real keywords within the slug of the original article. If it contains none (for example, only contains random characters), generate a short slug from the article you link to. In this case, your own "link shortener" could produce
#
bkil
my.example/x/social-network-taxonomy that you would reference in each of your articles.
geoffo and bterry joined the channel
#
GWG
[manton]: Thanks for the feedback
aaronpk joined the channel
#
bkil
capjamesg: I think micro QR support is less common than for normal QR and it doesn't save that much in many cases. Also, a trick to allow generating smaller and less dense QR codes is to reduce both the length and the entropy within your URL. You can save a bunch if you uppercase the protocol and host part (and use HTTP instead of HTTPS) And if possible, in the path portion, stick to either all-numeric or the all-alphanumeric set `[0-9A-Z $%*+./:-]`.
#
bkil
This is the longest URL you can fit in the least dense version 1 QR code: HTTP://A.EXAMPLE/123456789
#
IWDiscordRelay
<c​apjamesg#4492> I need like 50-60 chars.
#
bkil
Oh wow, I'd call a 60 character URL humongous! What do you encode in the URI, frontend and backend code for the whole web app? 😉 https://github.com/bkil/private-plugin.php
#
bkil
The above URL was just 42 characters. 41 with HTTP. I also dislike the scheme used by most mediawiki installations as they are very redundant for tiny permalinks as well.
#
capjamesg
domain/yyyy/mm/dd/slug
#
Loqi
[preview] [James] Source transparency in LLM information retrieval systems
#
bkil
Results in a 29x29 code with the origin upper cased (33x33 as is). The above v1 is 21x21
#
bkil
Using the largest (v4: 17x17) micro QR, I could only fit HTTP://JAMESG.BLOG/XY
#
capjamesg
Interesting.
#
bkil
d%7D
#
bkil
Can you scan it?
[chrisbergr] joined the channel
#
bkil
So as you have such a pretty long domain name, you can only publish 2048 articles using micro QR. You can sometimes find a 4 or 5 character domain and a 2 character (local) TLD pretty cheap if this is your thing, but I probably wouldn't bother.
#
bkil
The question is, is it feasible for you to redirect all upper case slugs to their lower cased versions (i.e., making your paths case insensitive)? Can you spare the day of month from an entry? Can you spare the trailing slash?
[KevinMarks], jjuran and ben_thatmustbeme joined the channel
#
[tantek]
what is URL design
#
Loqi
URL design is the practice of deliberately designing URLs, in particular, permalinks, typically for a better UX for everyone who creates, reads, and shares content https://indieweb.org/URL_design
#
[tantek]
^ more there
[tw2113_Slack_] joined the channel