Jermolene
Request: Feature rich embedded links
TiddlyWiki should of course feature rich embedded links!
I made http://richlinks.tiddlyspot.com/ which clearly demonstrates what is possible.
This is BIG BANG for the buck - much cool stuff that should attract users, for really a very small effort.
How? - in the About tiddler in that link, check out the tab "Alternatives" that talks about oEmbed and Noembed which might just be usable for TW?
copied over from my groups response:
Not really a fan of this being default. ... eg: If you load content from 3rd parties like ths, you ping them and provide a whole load of information about your current status and activity. eg: IP address used, which gives a good approximation of your current location. Content, that you are interested in, at the current moment ... and so on.
This is a nice plugin, and it should stay that way! Everyone, who wants to use it, should be able to do so. ... AND ... everyone, who doesn't want to expose private information, should be free to do so as well.
just my 2cents mario
@pmario - also copying my reply form the group:
Let's not throw out the baby with the bath water. The core wouldn't necessarily have to provide any "pinging" templates at all. It could feature the equivalent of the richlink main macro and the (customizable) dictionary, without templates... but, it could (should!) IMO provide at least templates for local files. Many people want to show e.g pdf documents and it would be super simple for people to make e.g nice image albums or audio or video libraries for local files.
...AND if the user does want the pinging commercial services, then he can rather easily add those too.
Follow up:
oEmbed (github) would be a spot-on solution to an otherwise pretty thin(!) TW embed functionality.
This is how it would work: The TW user pastes a link to some service (e.g a Spotify track). TW remakes this into into an oEmbed link for that service by means of the oEmbed providers list. The service site sends back a standardized JSON or XML string that TW can process.
Noembed also seems great but it works as a middle-man for oEmbed; it adds the Noembed prefix url and instead of the end service (eg Spotify) sending you the object, it goes via noembed.com. Advantages include that it tweaks the response, which apparently is only JSON. It also includes more sources than oEmbed. BUT it is a 3d part whereas oEmbed is directly with the service provider, if I understand.
As noted in a forum post one could imagine a setting in TW, similar to this one:
...but for external links
- Embed external links where possible
- Always display external links as plain links
This feels like such a low hanging fruit to display the power of TW, People can immediately understand the value of it.
This is indeed big bang for the buck, but I agree... entirely plugin territory, especially considering that the actual representation needs may very well vary for each supported service.
It's almost 2026, plz add such thing as default.
IMO it is bloat for the core (since not many people use it, and it requires a split operator plugin), and a wide range of tiddlywiki users do care about core size. I don't think there is clear benefit of including it in the core compared to installing it manually.
