blog issueshttps://gitlab.torproject.org/tpo/web/blog/-/issues2021-11-22T14:28:58Zhttps://gitlab.torproject.org/tpo/web/blog/-/issues/40031Broken image links2021-11-22T14:28:58ZGusBroken image linksSome images aren't loading in this [blog post](https://blog.torproject.org/tor-project-membership-program/).
The images were migrated, but the URLs are slightly different, for example:
https://blog.torproject.org/static/images/blog/in...Some images aren't loading in this [blog post](https://blog.torproject.org/tor-project-membership-program/).
The images were migrated, but the URLs are slightly different, for example:
https://blog.torproject.org/static/images/blog/inline-images/Quote%20%233.png
https://blog.torproject.org/static/images/blog/inline-images/Quote%20#3.pngJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40030events feed gives 4042021-11-19T13:02:17Zemmapeelevents feed gives 404Ey there:
The atom feed at https://blog.torproject.org/events.xml is not working anymore.
This breaks the build of the community portal because it uses it to render https://community.torproject.org/outreach/ .
see:
https://gitlab.tor...Ey there:
The atom feed at https://blog.torproject.org/events.xml is not working anymore.
This breaks the build of the community portal because it uses it to render https://community.torproject.org/outreach/ .
see:
https://gitlab.torproject.org/tpo/web/community/-/blob/main/templates/outreach.html#L38Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40029Comments section - "User support forum" is linking to the blog post instead o...2021-11-18T13:20:24ZGusComments section - "User support forum" is linking to the blog post instead of forum.tpn"If you are looking for support, please see our [FAQ](https://support.torproject.org/), [user support forum](https://blog.torproject.org/run-a-bridge-campaign/) or ways to [get in touch with us](https://www.torproject.org/contact)."
`us..."If you are looking for support, please see our [FAQ](https://support.torproject.org/), [user support forum](https://blog.torproject.org/run-a-bridge-campaign/) or ways to [get in touch with us](https://www.torproject.org/contact)."
`user support forum` should link to forum.tpnhttps://gitlab.torproject.org/tpo/web/blog/-/issues/15032Make blog.torproject.org mirrorable2021-11-18T03:02:01ZTracMake blog.torproject.org mirrorableThe blog at blog.torproject.org is an essential part of the torproject website that many users may want to visit. Though currently, mirror operators do not (cannot) mirror it due to its dynamic content (commenting capability). I suggest ...The blog at blog.torproject.org is an essential part of the torproject website that many users may want to visit. Though currently, mirror operators do not (cannot) mirror it due to its dynamic content (commenting capability). I suggest that we implement a method of exporting a static copy of the blog that can be mirrored.
**Trac**:
**Username**: martingaleJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40025Fix relative URLs in RSS/Atom feeds2021-11-17T21:21:47ZJérôme Charaouilavamind@torproject.orgFix relative URLs in RSS/Atom feedsAssets referred to in the feeds like lead and inline images are being generated with a relative URL. In a RSS/Atom feed, those need to be absolute.Assets referred to in the feeds like lead and inline images are being generated with a relative URL. In a RSS/Atom feed, those need to be absolute.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40024Blog post for Nov. 17 20212021-11-17T15:20:37Zal smithBlog post for Nov. 17 2021Hi @lavamind, as requested in #40004, here is my markdown-formatted text for a blog post tomorrow: https://pad.riseup.net/p/lCIhz9DHw9x8q7CQ-iDL, and here is the asset / blog header image i'd like to use:
![yec-social-slogan-dark](/uplo...Hi @lavamind, as requested in #40004, here is my markdown-formatted text for a blog post tomorrow: https://pad.riseup.net/p/lCIhz9DHw9x8q7CQ-iDL, and here is the asset / blog header image i'd like to use:
![yec-social-slogan-dark](/uploads/1e0f35f66b79e03c6708516dc1ccda40/yec-social-slogan-dark.png)Jé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/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/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/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/22397Add a (single) onion service for the new tor blog2021-11-16T14:10:59ZteorAdd a (single) onion service for the new tor blogWhen we asked for this for the old blog, it wasn't technically feasible (or it was a legacy system, so we decided not to do it).
I hope that onion service compatibility (mainly URL rewrites) was one of the requirements for the new blog.When we asked for this for the old blog, it wasn't technically feasible (or it was a legacy system, so we decided not to do it).
I hope that onion service compatibility (mainly URL rewrites) was one of the requirements for the new blog.Launch support's Forum and Blog migrationJé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/27566Missing link anchor for paginated comments2021-11-15T16:41:27ZtraumschuleMissing link anchor for paginated commentsClicking on the FIRST and LAST links for paginated comments does not jump down to the comments.Clicking on the FIRST and LAST links for paginated comments does not jump down to the comments.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/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/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/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/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/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