Changes after getting a Mastodon account

[egekorkan]

• Updating all WoT Repository readmes (adding Mastodon button while keeping Twitter)
• Website update (Main Page): Should we replace the Twitter embed with Mastodon? The discussion from the meeting of 19.12 is to replace it but also put a "We are also on Twitter" button under it. Keeping both would not look nice since the text is the same.
• Website update (Contact Page): Adding Mastodon
• Updating Twitter profile to point to Mastodon

[JKRhb]

One thing we could also consider is adding a rel="me" link to the website to "verify" our Mastodon account (c.f. https://joinmastodon.org/verification).

[egekorkan]

#466 #463 and #462 fix most of the points above. Separately, I have updated our Twitter profile (https://twitter.com/W3C_WoT) to link to our Mastodon account as requested by MarComm team.

[egekorkan]

The first point above mentions all repos but as indicated in #462, I will do that once that is merged to avoid updating a PR in all repos.

[egekorkan]

All points but the first one are done now.

[egekorkan]

The first point is going to be addressed in #476

[egekorkan]

We will split this work where different people will create the corresponding PRs at the repositories. The template is available at https://github.com/w3c/wot/blob/main/README.template.md

• TD: @egekorkan Readme alignment wot-thing-description#2016
• Binding Template: @egekorkan Align Readme wot-binding-templates#365
• Profiles: @lu-zero Update readme with the link to mastodon wot-profile#409
• Scripting API: @danielpeintner refactor: align with latest version of WoT README template wot-scripting-api#550
• Discovery: @relu91 (a resolution in the main call might be necessary since the TF is paused) Alling Readme to template wot-discovery#545
• Use Cases: @egekorkan
• Architecture
• Security
• WoT Resources: @danielpeintner refactor: Align Readme to template wot-resources#23
• Temporary TD repository for tooling