hi
since in every esp-idf update files and links renames, changed and new sorted are absolutely necessary
and on the base posted links in past then get '404'
perhabs it would be a good overthink to use a forwarder service?
do you have any plan or idea how we can manage this?
example:
if we post links in twitter/postings like this:
https://twitter.com/ESP32net/status/820860929797738496
or
this
https://twitter.com/eMbeddedHome/status ... 1327314944
or forum post
http://esp32.com/viewtopic.php?f=18&p=4306#p3935
all links in this get now '404'
do you know a good forwarder service that we can edit the target links every time simpley
and use a simpley forward link in our post?
will test this, can we edit later every time the target ( destination ) ?
http://tinyurl.com/
https://bitly.com/
edit: it looks like we can't edit destination link later with this services
best wishes
rudi
proposal: forwarder service for links
proposal: forwarder service for links
-------------------------------------
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪
love it, change it or leave it.
-------------------------------------
問候飛出去的朋友遍全球魯迪
Re: proposal: forwarder service for links
It's pretty simple: don't post links to tree/master, point to the exact commit ID or tag:
https://github.com/espressif/esp-idf/tr ... ocols/mdns
(FWIW, we have the same problem with our readthedocs documentation, which needs to be addressed, but in an automated way).
https://github.com/espressif/esp-idf/tr ... ocols/mdns
(FWIW, we have the same problem with our readthedocs documentation, which needs to be addressed, but in an automated way).
Who is online
Users browsing this forum: Baidu [Spider] and 113 guests