blog issueshttps://gitlab.torproject.org/tpo/web/blog/-/issues2021-08-31T13:55:31Zhttps://gitlab.torproject.org/tpo/web/blog/-/issues/40006Add markup for sharing links on social media sites2021-08-31T13:55:31ZdonutsAdd markup for sharing links on social media sitesComms often have to create and upload separate images when sharing links on Facebook, Twitter and Mastodon as our current blog posts don't generate link previews on the timeline.
To reduce this effort, could we add the appropriate share...Comms often have to create and upload separate images when sharing links on Facebook, Twitter and Mastodon as our current blog posts don't generate link previews on the timeline.
To reduce this effort, could we add the appropriate share metatags for the following platforms:
- [Facebook](https://developers.facebook.com/docs/sharing/webmasters#markup)
- [Twitter](https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/markup)
- [Mastodon](https://docs.joinmastodon.org/entities/card/) (it seems this uses Opengraph too, so no further action may be necessary)
Full-sized cards featuring the blog post's title, description and banner image would be great, please.Launch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40005Drupal blog: function deprecation message2021-07-08T19:03:50ZMatthew FinkelDrupal blog: function deprecation messageAfter submitting a form, the blog shows:
```
Deprecated function: Function create_function() is deprecated in GeSHi->_optimize_regexp_list_tokens_to_string() (line 4698 of vendor/geshi/geshi/src/geshi.php).
```After submitting a form, the blog shows:
```
Deprecated function: Function create_function() is deprecated in GeSHi->_optimize_regexp_list_tokens_to_string() (line 4698 of vendor/geshi/geshi/src/geshi.php).
```Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40004Migrate the blog out of Drupal and into a static site generator with a commen...2022-01-26T16:56:00ZGabagaba@torproject.orgMigrate the blog out of Drupal and into a static site generator with a comment service### Content
* [x] Import blog posts from Drupal
* [x] Import events from Drupal
* [x] Import comment archive
* [x] Configure RSS/Atom feeds (posts + events)
* [x] Implement categories to replace tags (depends on https://gitlab.torp...### Content
* [x] Import blog posts from Drupal
* [x] Import events from Drupal
* [x] Import comment archive
* [x] Configure RSS/Atom feeds (posts + events)
* [x] Implement categories to replace tags (depends on https://gitlab.torproject.org/tpo/web/blog/-/issues/40008)
* [x] Test Discourse comments embedding (depends on https://gitlab.torproject.org/tpo/tpa/team/-/issues/40183)
* [x] Test draft post feature
### Layout
* [x] Import relevant CSS styles from old blog
* [x] Setup 2-column responsive layout
* [x] Mirror header and footer contents from other Tor websites
### Deployment
* [x] Ensure functioning newsletter image URL redirections ([example](https://newsletter.torproject.org/archive/2021-11-01-privacy-is-a-human-right/))
* [x] Plan/implement publishing moratorium and comments section closure on Drupal
* [x] Full, final content import from Drupal
* [x] Setup static web mirrors for new site
* [x] Transition `blog.torproject.org` address
* [x] Fossilize old Drupal site (tpo/web/blog#40011)
* [ ] ~~Wind down Pantheon subscription~~ (tpo/tpa/team#40526)
* [ ] ~~Retire (or reconfigure) cache*.torproject.org machines~~ (tpo/tpa/team#40527)
### Workflow
* [x] Implement Review Apps for easy MR previews
* [x] Document final publishing workflow of the new blog
Documentation of the project requirements lives at https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/blogLaunch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.org2021-11-17https://gitlab.torproject.org/tpo/web/blog/-/issues/40003Fix blog comment indentation2021-07-13T22:56:26ZcypherpunksFix blog comment indentationThe comment threads on the blog became improperly indented in early 2021. In the more egregious cases, the box in which to write a comment is indented as well. Examples:
* https://blog.torproject.org/tor-bug-smash-fund-yr2-progress#comm...The comment threads on the blog became improperly indented in early 2021. In the more egregious cases, the box in which to write a comment is indented as well. Examples:
* https://blog.torproject.org/tor-bug-smash-fund-yr2-progress#comments
* https://blog.torproject.org/new-release-tor-browser-10012#comments
* https://blog.torproject.org/new-release-tor-browser-105a11#comments
* https://blog.torproject.org/new-release-tor-browser-10013#comments
* https://blog.torproject.org/new-release-tor-browser-105a12#comments
* https://blog.torproject.org/new-release-tor-browser-10014#comments
* https://blog.torproject.org/new-release-tor-browser-10015#comments
* https://blog.torproject.org/new-release-tor-browser-105a14#commentshttps://gitlab.torproject.org/tpo/web/blog/-/issues/40002Reduce the file size of PNG banner images2021-11-16T23:29:26ZcypherpunksReduce the file size of PNG banner imagesMost images on the blog are PNG and very large file size for the web. They make browsing the blog particularly bad for mobile and in situations where internet speed is low, throttled, or capped. Most of the images do not need the clarity...Most images on the blog are PNG and very large file size for the web. They make browsing the blog particularly bad for mobile and in situations where internet speed is low, throttled, or capped. Most of the images do not need the clarity of a PNG and would remain visibly understandable as a smaller file size JPG. You can archive PNGs that you think you might edit in the future, but don't embed large file sizes on high-traffic pages, particularly not in the headers of blog posts. Convert them to JPG except for the few that absolutely cannot be visibly understood in a [lossy compression](https://en.wikipedia.org/wiki/Lossy_compression) format.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40001Tor logo does not direct to the homepage2021-04-02T16:41:29Zkulsoom.zahrakulsoomzahra24@gmail.comTor logo does not direct to the homepageTor logo at https://blog.torproject.org/ does not direct to [homepage](https://torproject.org/)Tor logo at https://blog.torproject.org/ does not direct to [homepage](https://torproject.org/)https://gitlab.torproject.org/tpo/web/blog/-/issues/40000Gitlab Migration Milestone2020-06-13T17:10:53ZTracGitlab Migration MilestoneWe're creating this ticket as a part of the Trac-to-Gitlab migration, so that each project's numbering for new tickets will start with 40001.We're creating this ticket as a part of the Trac-to-Gitlab migration, so that each project's numbering for new tickets will start with 40001.https://gitlab.torproject.org/tpo/web/blog/-/issues/33115Migrating the blog to a static web site with Lektor2021-07-22T19:30:16ZHiroMigrating the blog to a static web site with LektorWe have been having issues with the blog for a long time. The template we are using was developed for another purpose and never really finished.
We also spend a lot of money on Drupal that could rather be spent somewhere else.
I propose...We have been having issues with the blog for a long time. The template we are using was developed for another purpose and never really finished.
We also spend a lot of money on Drupal that could rather be spent somewhere else.
I propose to migrate the blog to a static website with lektor and have comments running from discourse.org. I have actually been in contact with discourse and they have offered to run a forum for us for free (legacy/trac#33105). Addittionally they would run an .onion and a torproject.org subdomain.
Moderation on discourse is much easier than on drupal comments (another pain point for the blog), and we would get a forum that we could use for other purposes too.
This is how the blog can be migrated.
- We will do mockups and approve them with all the parties involved.
- We will start migrating content and have it on staging for testing.
- Once we are happy we will archive the current blog into static pages and move the static bloc to blog.torproject.org.
What we will lose:
- Version history on posts.
- Old comments. I see no value in migrating old blog comments to discourse to be honest. It would be a lot of effort and the old comments will be archived anyways in the blog archive.
What we will gain:
- Once the blog has been migrated creating posts will be no different than editing anyone of our websites. It would actually be a bit easier since there are a few different template and pages in our website and the blog will just have posts.
- Anyone that is currently updating the websites will be able to help people with blog posts, therefore we will gain a lot more of blog admins.
- The blog will run from our static www rotation, so we will not have to run expensive services or 2 cache VMs in front of it to avoid paing a lot to a third party for page views.
- We will not have to update a service every now and again. The blog will run out of static HTML.
- We will be able to update the templates according to our styleguide.
- Functionalities that we will build won't break because of a drupal update.Launch support's Forum and Blog migrationHiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/33109Make (and then use) a blog account policy2021-01-07T20:52:34ZRoger DingledineMake (and then use) a blog account policyWe have a bunch of old accounts on the blog, and for basic security hygiene, we should clean them up.
Even better, let's take this chance to develop, and post somewhere, a policy for who should be able to have a blog account, and when w...We have a bunch of old accounts on the blog, and for basic security hygiene, we should clean them up.
Even better, let's take this chance to develop, and post somewhere, a policy for who should be able to have a blog account, and when we'll disable them due to inactivity or etc.
Here is a proposed start to such a policy:
* Any Tor Core Contributor can get a blog account, and it can stay active as long as they remain a core contributor.
https://gitweb.torproject.org/community/policies.git/tree/membership.txt
* We encourage everybody with an active blog account to do blog posts. Before you post, please work with the comms team to make sure the timing and content are best. [replace this short text with the longer text from steph's comment below]
* To limit security surface area, we will disable accounts that haven't logged in during the past n months. Accounts can always be re-enabled when people want to use them again.
(I suggest n=18 months. We should specify some avenue for how to request the account in the first place, and for how to request re-enabling.)
* Posters should be aware of, and follow, our blog comment moderation strategy:
https://trac.torproject.org/projects/tor/wiki/doc/community/blog-comment-policy
* We encourage guest posts from the broader community about topics that are important to Tor and Tor users. The best way to arrange a guest post is to get an existing Core Contributor to vouch for the guest, and then depending on the situation, either the core person will post it, or we'll make a blog account for the guest.Isabela FernandesIsabela Fernandeshttps://gitlab.torproject.org/tpo/web/blog/-/issues/33105evaluate if discourse can be used as comments platform for the blog2020-06-27T14:29:54ZHiroevaluate if discourse can be used as comments platform for the blogI have been in contact with discourse.org and they have offered to run a discourse forum for us under a tp.o subdomain. They have also offered to setup a .onion.
Discourse can be a perfect solution to use for our blog comments in case w...I have been in contact with discourse.org and they have offered to run a discourse forum for us under a tp.o subdomain. They have also offered to setup a .onion.
Discourse can be a perfect solution to use for our blog comments in case we want to migrate our blog to static.
We need to evaluate if discourse is loading any third-party service that might expose our user to unnecessary tracking.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/32874Tor blog tags not showing up on mobile2021-11-16T23:30:49ZTracTor blog tags not showing up on mobileWhile loading the Tor Blog on mobile browsers the tags of each article don't show up.
**Trac**:
**Username**: annalee_While loading the Tor Blog on mobile browsers the tags of each article don't show up.
**Trac**:
**Username**: annalee_https://gitlab.torproject.org/tpo/web/blog/-/issues/32288https://support.torproject.org/get-in-touch/how-can-i-get-support/ in our "Jo...2020-06-27T14:29:54ZGeorg Koppenhttps://support.torproject.org/get-in-touch/how-can-i-get-support/ in our "Join the discussion" footer on our blog is giving a 404A user [reported](https://blog.torproject.org/comment/284719#comment-284719) that https://support.torproject.org/get-in-touch/how-can-i-get-support/ gives a 404. It can be found in the "Join the discussion" section on our blog.
Not sure...A user [reported](https://blog.torproject.org/comment/284719#comment-284719) that https://support.torproject.org/get-in-touch/how-can-i-get-support/ gives a 404. It can be found in the "Join the discussion" section on our blog.
Not sure what to do here but it got suggested we use a different link on our blog, like https://www.torproject.org/contact/.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/31809blog comments misformatted; incorrect <div> nesting?2020-06-27T14:29:54ZTaylor Yublog comments misformatted; incorrect <div> nesting?A user on IRC reports that some comments on https://blog.torproject.org/join-global-climate-strike-20-27-september seem to be overflowing their margins.
It looks like comments beyond a certain number are no longer contained in the corre...A user on IRC reports that some comments on https://blog.torproject.org/join-global-climate-strike-20-27-september seem to be overflowing their margins.
It looks like comments beyond a certain number are no longer contained in the correct `<div>`?
Another post that shows this behavior is https://blog.torproject.org/browser-fingerprinting-introduction-and-challenges-ahead
I see this on Tor Browser; I haven't checked with other browsers yet. The content nesting in the HTML definitely seems consistent with the behavior though.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/31710Write blog post about the digital climate strike, and how Tor makes activists...2020-06-27T14:29:55ZteorWrite blog post about the digital climate strike, and how Tor makes activists saferWe want to write a blog post about:
* Tor's participation in the Digital Climate Strike, and
* How using Tor makes climate activists saferWe want to write a blog post about:
* Tor's participation in the Digital Climate Strike, and
* How using Tor makes climate activists saferteorteorhttps://gitlab.torproject.org/tpo/web/blog/-/issues/31114Threading in blog comments is hardly visible and blog comment formatting is b...2020-06-30T11:11:16ZGeorg KoppenThreading in blog comments is hardly visible and blog comment formatting is brokenProbably due to the recent Drupal security upgrade the threading in blog comments is hard to follow and blog comment formatting is broken. This makes interacting with our blog pretty painful.Probably due to the recent Drupal security upgrade the threading in blog comments is hard to follow and blog comment formatting is broken. This makes interacting with our blog pretty painful.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/30576If permissions.default.image is set to 2 and one comments on a blog post it k...2020-06-27T14:29:55ZcypherpunksIf permissions.default.image is set to 2 and one comments on a blog post it keeps reloadingHiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/30358Redirect season of docs blog link2020-06-27T14:29:55ZstephwRedirect season of docs blog linkRedirect https://blog.torproject.org/google-season-docs-2019
to https://blog.torproject.org/google-season-docs-2019-help-tor-improve-our-documentation
Both links have been shared as the correct link.Redirect https://blog.torproject.org/google-season-docs-2019
to https://blog.torproject.org/google-season-docs-2019-help-tor-improve-our-documentation
Both links have been shared as the correct link.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/29735create blog account for juga2020-06-27T14:29:55Zstephwcreate blog account for jugajuga at torproject
nickname: jugajuga at torproject
nickname: jugaHiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/29685Create a blog account for Gaba2020-06-27T14:29:55ZstephwCreate a blog account for Gabagaba @ torproject.org
username: Gabagaba @ torproject.org
username: GabaHiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/29619Add comment policy to the blog2020-06-27T14:29:55ZstephwAdd comment policy to the blogAdd a comment policy to the blog above the comment field so it'll be visible on each post beneath "Join the discussion."
Note: only "join the discussion" remains visible from the blog archive. The new text is only visible inside each p...Add a comment policy to the blog above the comment field so it'll be visible on each post beneath "Join the discussion."
Note: only "join the discussion" remains visible from the blog archive. The new text is only visible inside each post.
"Join the discussion...
We encourage respectful, on-topic comments. Comments that violate our [Code of Conduct](https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.txt) will be deleted. Off-topic comments may be deleted at the discretion of the post moderator. Please do not comment as a way to receive support or report bugs on a post unrelated to a release. If you are looking for support, please see our [support portal](https://support.torproject.org/) or ways to [get in touch with us](https://trac.torproject.org/projects/tor/wiki/doc/community/HowToReportBugFeedback).HiroHiro