blog issueshttps://gitlab.torproject.org/tpo/web/blog/-/issues2022-03-09T23:22:53Zhttps://gitlab.torproject.org/tpo/web/blog/-/issues/40023Convert images to WebP at build-time2022-03-09T23:22:53ZJérôme Charaouilavamind@torproject.orgConvert images to WebP at build-timeTo improve user's experience on the site on mobile devices and/or the Tor network, we should reduce the size of image assets as much as possible. We [already compressed the PNGs](tpo/web/blog#40002) but further gains could be made by con...To improve user's experience on the site on mobile devices and/or the Tor network, we should reduce the size of image assets as much as possible. We [already compressed the PNGs](tpo/web/blog#40002) but further gains could be made by converting images to WebP during the website build. Furthermore, WebP support both lossy and lossless compression, as well as animations, so we'd be able to compress all of our PNG, JPG and GIF lead images to this format.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40022Text size issues on mobile Firefox and Tor Browser2021-11-16T23:17:25ZJérôme Charaouilavamind@torproject.orgText size issues on mobile Firefox and Tor BrowserThe headers and summary text size is unusually small on the first post, and some (not all) subsequent posts.
![signal-2021-11-16-155859_001](/uploads/eb6c1b549cd4b7b8538333a1bf072714/signal-2021-11-16-155859_001.png)The headers and summary text size is unusually small on the first post, and some (not all) subsequent posts.
![signal-2021-11-16-155859_001](/uploads/eb6c1b549cd4b7b8538333a1bf072714/signal-2021-11-16-155859_001.png)Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40021Auto rebuild and deploy on daily schedule2021-12-06T14:37:31ZJérôme Charaouilavamind@torproject.orgAuto rebuild and deploy on daily scheduleUnless we rebuild and deploy the site to production at least once on a daily basis, the **Upcoming Events** sidebar section is going to go stale, showing events which are in the past.
We should be able to do this by defining one or two ...Unless we rebuild and deploy the site to production at least once on a daily basis, the **Upcoming Events** sidebar section is going to go stale, showing events which are in the past.
We should be able to do this by defining one or two extra CI jobs and a CI/CD pipeline schedule.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40020Convert .txt RedirectMap to .dbm2022-01-06T16:18:11ZJérôme Charaouilavamind@torproject.orgConvert .txt RedirectMap to .dbmThe RedirectMaps we use, especially the one for comments, are large enough that they would probably benefit from being converted to hashed `.dbm` format which is indexed, contrary to `.txt`.
https://httpd.apache.org/docs/2.4/rewrite/rew...The RedirectMaps we use, especially the one for comments, are large enough that they would probably benefit from being converted to hashed `.dbm` format which is indexed, contrary to `.txt`.
https://httpd.apache.org/docs/2.4/rewrite/rewritemap.html#dbmJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40019Probably don't need a huge generic Tor image if the original blog post didn't...2021-11-15T16:05:18ZRoger DingledineProbably don't need a huge generic Tor image if the original blog post didn't have an imageThe tendency to put an image for our blog posts is somewhat new. It looks like the import uses a generic Tor picture if there isn't one already. This choice results in kind of weird old post lists, e.g. <br>
https://blog-staging.torproje...The tendency to put an image for our blog posts is somewhat new. It looks like the import uses a generic Tor picture if there isn't one already. This choice results in kind of weird old post lists, e.g. <br>
https://blog-staging.torproject.org/page/153/
Maybe it is cleaner to just not put a picture if there wasn't a picture?Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40018Not all posts imported with a given tag?2021-11-15T16:05:18ZRoger DingledineNot all posts imported with a given tag?Notice for the 'research' tag on the blog we have many posts: <br>
https://blog.torproject.org/category/tags/research
But then notice that for that same tag on the new blog, we have only 2 posts: <br>
https://blog-staging.torproject.org...Notice for the 'research' tag on the blog we have many posts: <br>
https://blog.torproject.org/category/tags/research
But then notice that for that same tag on the new blog, we have only 2 posts: <br>
https://blog-staging.torproject.org/category/research/
The other posts are *there* on the new blog, e.g. <br>
https://blog-staging.torproject.org/call-arms-helping-internet-services-accept-anonymous-users/ <br>
but they seem to have lost their tags.https://gitlab.torproject.org/tpo/web/blog/-/issues/40017Comment threading is lost on import2023-04-11T13:22:40ZRoger DingledineComment threading is lost on importIn the comments on <br>
https://blog.torproject.org/transparency-openness-and-our-2015-financials <br>
the indentation shows which comments are a reply to which other comments.
Whereas on <br>
https://blog-staging.torproject.org/transpa...In the comments on <br>
https://blog.torproject.org/transparency-openness-and-our-2015-financials <br>
the indentation shows which comments are a reply to which other comments.
Whereas on <br>
https://blog-staging.torproject.org/transparency-openness-and-our-2015-financials <br>
the indentation and threading is lost, and all the comments are just a flat list.
@lavamind says that the import actually does capture the indentation (yay), and maybe we need some extra CSS or something to help it to render properly.https://gitlab.torproject.org/tpo/web/blog/-/issues/40016Second page of comments doesn't get imported properly2021-11-15T16:40:00ZRoger DingledineSecond page of comments doesn't get imported properlyAt the bottom of <br>
https://blog-staging.torproject.org/next-chapter-anti-censorship/ <br>
there are some links to other pages of comments, but the links are 404s.
Compare to the bottom of <br>
https://blog.torproject.org/next-chapter...At the bottom of <br>
https://blog-staging.torproject.org/next-chapter-anti-censorship/ <br>
there are some links to other pages of comments, but the links are 404s.
Compare to the bottom of <br>
https://blog.torproject.org/next-chapter-anti-censorship <br>
where the link to "page 2" of the comments works properly.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40014Fix suboptimal page slugs2021-11-16T02:23:52ZJérôme Charaouilavamind@torproject.orgFix suboptimal page slugsTo avoid problems with duplicate slugs and missed content, `drupal2lektor` was [modified](https://gitlab.torproject.org/tpo/web/drupal2lektor/-/commit/b21a315d6b2c8f3189f0ca62cd15276a7f329683) to use the `node-[nid]` as the slug when a n...To avoid problems with duplicate slugs and missed content, `drupal2lektor` was [modified](https://gitlab.torproject.org/tpo/web/drupal2lektor/-/commit/b21a315d6b2c8f3189f0ca62cd15276a7f329683) to use the `node-[nid]` as the slug when a node was missing a URL alias in Drupal. Furthermore, some aliases containing a `blog/` or `events/` upper directory were changed to `blog-` and `events-`, again to prevent any issues with duplicate content cause missing pages.
Once the import is complete, we should go over those to generate a new URL slug based on the title, taking care to manage duplicates correctly (eg. by adding a suffix).Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40013Import Drupal redirects2021-11-15T19:45:47ZJérôme Charaouilavamind@torproject.orgImport Drupal redirectsThere are several redirects configured in the Drupal blog, we should add them to the new Lektor site as well.
|From|To|Statuscode|Date|
|----|--|----------|----|
/blog/network-team-hackfest-wilmington-ward |/blog/network-team-hackfest-...There are several redirects configured in the Drupal blog, we should add them to the new Lektor site as well.
|From|To|Statuscode|Date|
|----|--|----------|----|
/blog/network-team-hackfest-wilmington-ward |/blog/network-team-hackfest-wilmington-watch |301 |July 02, 2017 |
/blog/squashing-bugs-tor-bug-bounty-program |/blog/we-will-pay-you-to-hack-tor-bug-bounty |301 |July 14, 2017 |
/blog/de-anonymization-tor-home-and-erlang-tor-coming-sha2017 |/blog/de-anonymization-smart-homes-and-erlang-at-sha2017 |301 |July 24, 2017 |
/blog/test |/blog/tor-downloads-2017 |301 |August 21, 2017 |
/blog/were-upping-our-support-mobile-browsing |/blog/upping-support-mobile-browsing |301 |September 05, 2017 |
/report-bugs-get-atechdad |/report-bugs-get-money-like-atechdad |301 |September 29, 2017 |
/were-powering-digital-resistance-help-mozilla |/powering-digital-resistance-help-mozilla |301 |October 20, 2017 |
/tor-en-primavera-hacker-este-fin-de-semana-en-santiago-join-tor-primavera-hacker-santiago-next |/tor-en-primavera-hacker-este-fin-de-semana-en-santiago |301 |November 29, 2017 |
/explore-tor-nyc-meetup-ama-feb-15 |/explore-tor-nyc-meetup-feb-15 |301 |January 29, 2018 |
/contributors/nusenu-torblog |/user/120 |301 |February 05, 2018 |
/tor-project-joined-500000-duckduckgo-privacy-challenge-2018 |/tor-project-joined-duckduckgo-privacy-challenge-2018 |301 |March 13, 2018 |
/new-release-tor-browser-756 |/tor-browser-756-released- |301 |June 26, 2018 |
/tor-browser-756-released |/tor-browser-756-released- |301 |June 26, 2018 |
/tails-39-out |/tails-3.9-is-out |301 |September 05, 2018 |
/google-season-docs-2019 |/google-season-docs-2019-help-tor-improve-our-documentation |302 |May 02, 2019 |
/blog/google-season-docs-2019 |/google-season-docs-2019-help-tor-improve-our-documentation |302 |May 02, 2019 |
/tor-village-iff-call-proposals |/tor-village-iff-2020-call-proposals |301 |February 19, 2020 |
/new-release-tor-browser-958 |/new-release-tor-browser-95a8 |301 |March 17, 2020 |
/Lavoro-remoto-sicurezza-personale |/lavoro-remoto-sicurezza-personale |301 |March 26, 2020 |
/bridgedb-release-0-10-1 |/new-release-bridgedb-010-1 |301 |May 28, 2020 |
/wrapping-up-gsoc-2020 |/gsoc-2020-snowflake-proxy-mobile |301 |September 09, 2020 |
/tor-bug-smash-fund-2020-%24106K-raised |/tor-bug-smash-fund-2020-106K-raised |301 |September 17, 2020 |
/transparency-openness-and-our-2017-and-2018-financials |/transparency-openness-and-our-2018-and-2019-financials |301 |October 20, 2020 |
/stae-of-ipv6-support-tor-network |/state-of-ipv6-support-tor-network |301 |January 14, 2021 |
/ebook-defend-dissent-with-tor |/book-defend-dissent-with-tor |301 |April 26, 2021 |
/announcing-board-alissa-dees-kendra |/announcing-board-alissa-desigan-kendra |301 |May 26, 2021 |
/tor-0.4.6.2-alpha-released |/tor-0.4.7.1-alpha-released |301 |September 17, 2021 |
/new-release-tor-browser-110 |/new-release-tor-browser-11-0 |301 |November 10, 2021 |
https://blog.torproject.org/admin/config/search/redirectJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40011Fossilize old Drupal blog2021-12-13T19:21:54ZJérôme Charaouilavamind@torproject.orgFossilize old Drupal blogIt would be a good idea to fossilize and archive the old Drupal blog, it might come in handy eventually.
@anarcat had some ideas about how we can proceed.It would be a good idea to fossilize and archive the old Drupal blog, it might come in handy eventually.
@anarcat had some ideas about how we can proceed.Launch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40008Convert tags to smaller set of blog post categories2021-11-17T15:18:04ZJérôme Charaouilavamind@torproject.orgConvert tags to smaller set of blog post categoriesIn the process of migrating the Drupal site to Lektor, @duncan and I agreed it might make sense to replace the blog post tags with a predefined set of categories. This would simplify the Lektor site structure since we'd be able to forgo ...In the process of migrating the Drupal site to Lektor, @duncan and I agreed it might make sense to replace the blog post tags with a predefined set of categories. This would simplify the Lektor site structure since we'd be able to forgo the use of the `lektor-tags` module and allow us to provide RSS/Atom feeds of posts in each category.
The list of tags currently used on the blog is available here: https://pad.riseup.net/p/QqaP7feFvQlPJrDHmSyXLaunch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40007A very simple author's page2021-08-31T13:39:08ZGusA very simple author's pageAs we already have a tag page, can we have an authors' page, ie, a page that list all the blog posts made by someone?As we already have a tag page, can we have an authors' page, ie, a page that list all the blog posts made by someone?Launch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://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/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 migrationHiroHiro