Bug 272690 - Twitter no longer reliably available to the public
Summary: Twitter no longer reliably available to the public
Status: New
Alias: None
Product: Documentation
Classification: Unclassified
Component: Website (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-doc (Nobody)
URL: https://github.com/freebsd/freebsd-do...
Keywords: needs-patch
Depends on:
Blocks:
 
Reported: 2023-07-24 04:21 UTC by Graham Perrin
Modified: 2023-07-29 23:11 UTC (History)
1 user (show)

See Also:

Attachments
screenshot: https://twitter.com/freebsd no longer available to the public (134.53 KB, image/png)
2023-07-24 04:21 UTC, Graham Perrin 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Perrin 2023-07-24 04:21:56 UTC 
Created attachment 243580 [details]
screenshot: https://twitter.com/freebsd no longer available to the public

Let's not assume that publicity will return and persist. 

<https://old.reddit.com/r/technology/comments/14rmuyi/-/?sort=new> multiple users report an ongoing requirement to login.

In key areas of the website, add public-friendly alternatives to canonical twitter.com URLs. 

Likely candidates include: 

<https://nitter.net/freebsd>
<https://nitter.net/freebsdcore>
<https://nitter.net/FreeBSDHelp/>
Comment 1 Graham Perrin 2023-07-24 04:26:27 UTC 
(In reply to Graham Perrin ◐ from comment #0)

I have no Twitter account, I can't guess why: 

- <https://nitter.net/freebsd> is empty

- <https://nitter.net/freebsdcore> is empty (no item found) with 
  one pinned tweet.

Compared the emptiness above with <https://nitter.net/DLangille/>, which includes plenty of recent tweets.
Comment 2 Graham Perrin 2023-07-24 04:34:31 UTC 
(In reply to Graham Perrin ◐ from comment #0)

> … key areas of the website, …

No need to update things such as status reports.

Overview: 

% rg --count --sort path twitter.com /usr/doc
/usr/doc/documentation/themes/beastie/layouts/partials/site-head.html:1
/usr/doc/website/content/de/community/_index.adoc:1
/usr/doc/website/content/en/community/_index.adoc:2
/usr/doc/website/content/en/status/report-2009-04-2009-09.html:1
/usr/doc/website/content/en/status/report-2009-10-2009-12.html:2
/usr/doc/website/content/en/status/report-2010-01-2010-03.html:1
/usr/doc/website/content/en/status/report-2010-04-2010-06.html:2
/usr/doc/website/content/en/status/report-2010-07-2010-09.html:2
/usr/doc/website/content/en/status/report-2010-10-2010-12.html:2
/usr/doc/website/content/en/status/report-2011-01-2011-03.html:2
/usr/doc/website/content/en/status/report-2011-04-2011-06.html:2
/usr/doc/website/content/en/status/report-2011-07-2011-09.html:2
/usr/doc/website/content/en/status/report-2011-10-2011-12.html:2
/usr/doc/website/content/en/status/report-2012-01-2012-03.html:2
/usr/doc/website/content/en/status/report-2012-04-2012-06.html:2
/usr/doc/website/content/en/status/report-2012-07-2012-09.html:2
/usr/doc/website/content/en/status/report-2012-10-2012-12.html:2
/usr/doc/website/content/en/status/report-2013-01-2013-03.html:2
/usr/doc/website/content/en/status/report-2013-07-2013-09.html:2
/usr/doc/website/content/en/status/report-2013-10-2013-12.html:2
/usr/doc/website/content/en/status/report-2014-01-2014-03.html:2
/usr/doc/website/content/en/status/report-2014-04-2014-06.html:2
/usr/doc/website/content/en/status/report-2014-07-2014-09.html:2
/usr/doc/website/content/en/status/report-2014-10-2014-12.html:2
/usr/doc/website/content/en/status/report-2015-01-2015-03.html:2
/usr/doc/website/content/en/status/report-2015-04-2015-06.html:2
/usr/doc/website/content/en/status/report-2015-07-2015-09.html:2
/usr/doc/website/content/en/status/report-2016-04-2016-06.html:2
/usr/doc/website/content/en/status/report-2016-07-2016-09.html:2
/usr/doc/website/content/en/status/report-2016-10-2016-12.html:2
/usr/doc/website/content/en/status/report-2017-01-2017-03.html:2
/usr/doc/website/content/en/status/report-2017-04-2017-06.html:4
/usr/doc/website/content/en/status/report-2017-07-2017-09.html:2
/usr/doc/website/content/en/status/report-2017-10-2017-12.html:2
/usr/doc/website/content/en/status/report-2018-01-2018-09.html:2
/usr/doc/website/content/en/status/report-2019-10-2019-12.html:2
/usr/doc/website/content/en/status/report-2020-10-2020-12.html:1
/usr/doc/website/content/ja/community/_index.adoc:1
/usr/doc/website/content/ru/community/social.adoc:1
/usr/doc/website/content/zh-cn/community/_index.adoc:1
/usr/doc/website/content/zh-tw/community/_index.adoc:1
/usr/doc/website/data/en/usergroups/usergroups.toml:2
/usr/doc/website/static/security/patches/EN-18:14/tzdata-2018g.patch:2
/usr/doc/website/static/security/patches/EN-19:12/tzdata-2019b.patch:1
/usr/doc/website/static/security/patches/SA-20:19/unbound.11.3.patch:2
/usr/doc/website/static/security/patches/SA-20:19/unbound.12.1.patch:2
/usr/doc/website/themes/beastie/layouts/partials/sidenav.html:1
%
Comment 3 Edward.Sanford.Sutton, III 2023-07-29 23:11:07 UTC 
I don't do much with twitter or nitter, but in my experience nitter is intermittent both before and after twitter sign ins were required. The results can lead to blank or single post nitter pages instead of a proper full page and a refresh of the page 'may' change that. When it works its been a more pleasant experience as it cuts out the uselessness like javascript among other things.