blog issueshttps://gitlab.torproject.org/tpo/web/blog/-/issues2022-03-23T10:54:45Zhttps://gitlab.torproject.org/tpo/web/blog/-/issues/40039Please add this meta tag to blog.torproject.org for monetization w/ coil2022-03-23T10:54:45ZIsabela FernandesPlease add this meta tag to blog.torproject.org for monetization w/ coilHello we have set up a wallet to receive contributions through coil. The goal is to add this meta tag to our torproject.org and blog.torproject.org so we can receive contributions in coil.
The tag:
`<meta name="monetization" content="$...Hello we have set up a wallet to receive contributions through coil. The goal is to add this meta tag to our torproject.org and blog.torproject.org so we can receive contributions in coil.
The tag:
`<meta name="monetization" content="$ilp.uphold.com/pYfXb92JBQN4">`
More information about coil meta tags:
https://help.coil.com/docs/monetize/content/websites-monetize-sitehttps://gitlab.torproject.org/tpo/web/blog/-/issues/40038Fix missing events in review builds2022-02-23T22:17:53ZJérôme Charaouilavamind@torproject.orgFix missing events in review buildsThe `partial-build` flags we use for review app builds is moving aside future events that we should be able to preview.
Example: https://gitlab.torproject.org/tpo/web/blog/-/merge_requests/39The `partial-build` flags we use for review app builds is moving aside future events that we should be able to preview.
Example: https://gitlab.torproject.org/tpo/web/blog/-/merge_requests/39Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40037Pages with periods in the slug are served as plaintext2022-02-02T14:44:56ZJérôme Charaouilavamind@torproject.orgPages with periods in the slug are served as plaintextExample: https://blog.torproject.org/tor-0.4.7.1-alpha-released
This is by design in Lektor, according to the [docs](https://www.getlektor.com/docs/content/urls/):
> If however the last path component contains a period (.) then the las...Example: https://blog.torproject.org/tor-0.4.7.1-alpha-released
This is by design in Lektor, according to the [docs](https://www.getlektor.com/docs/content/urls/):
> If however the last path component contains a period (.) then the last path component is assumed to be a filename directly.
The solution is to replace the periods (.) with dashes (-) in directories under `content/blog` and also in the redirect files. The old URLs with periods will need a redirection in Apache.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40036GitLab Web IDE commits ignore LFS2022-06-08T15:12:54ZJérôme Charaouilavamind@torproject.orgGitLab Web IDE commits ignore LFSGot this warning when checking out the repository after 3ac9e793cb9f419b4a875f83219c25c59c37d6f8 was merged:
Encountered 1 file(s) that should have been pointers, but weren't:
content...Got this warning when checking out the repository after 3ac9e793cb9f419b4a875f83219c25c59c37d6f8 was merged:
Encountered 1 file(s) that should have been pointers, but weren't:
content/blog/tor-censorship-in-russia/lead.png
It turns out that when creating a commit using the Web IDE, LFS is just [ignored](https://docs.gitlab.com/ee/user/project/web_ide/#limitations):
> LFS files can be rendered and displayed but they cannot be updated and committed using the Web IDE. If an LFS file is modified and pushed to the repository, the LFS pointer in the repository is overwritten with the modified LFS file content.
Since we track image assets using LFS in the repository, this puts into question the use of the Web IDE as part of the authoring process, unfortunately...Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40035broken image links from old blog posts2022-02-02T14:44:56ZRoger Dingledinebroken image links from old blog postshttps://blog.torproject.org/update-internet-censorship-iran/ <br>
has links to images on blog.torproject.org and those links are broken.https://blog.torproject.org/update-internet-censorship-iran/ <br>
has links to images on blog.torproject.org and those links are broken.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40034Redirection loop2021-12-07T12:10:56ZGusRedirection loopWe have a redirection loop here:
https://blog.torproject.org/lifecycle-new-relay/
After this commit:
https://gitlab.torproject.org/tpo/web/blog/-/commit/d07cd61464734e57fed31251598954c5811d70a1We have a redirection loop here:
https://blog.torproject.org/lifecycle-new-relay/
After this commit:
https://gitlab.torproject.org/tpo/web/blog/-/commit/d07cd61464734e57fed31251598954c5811d70a1https://gitlab.torproject.org/tpo/web/blog/-/issues/40033Blog posts with duplicated list items on the Tor Forum2022-06-02T14:32:27ZGusBlog posts with duplicated list items on the Tor ForumI published a new blog post, but in Discourse, it's showing a duplicate list of items:
```
<p>Next steps include the following:</p><ul>
<li>Complete partial Certificate Transparency enforcement in Firefox. This would bring Certificate T...I published a new blog post, but in Discourse, it's showing a duplicate list of items:
```
<p>Next steps include the following:</p><ul>
<li>Complete partial Certificate Transparency enforcement in Firefox. This would bring Certificate Transparency with trusted logs to both Firefox and Tor Browser.</li>
<li>Create and implement a torspec proposal that uses Tor relays to increase your confidence that public logging actually happened when using Tor Browser.</li>
</ul><li>Complete partial Certificate Transparency enforcement in Firefox. This would bring Certificate Transparency with trusted logs to both Firefox and Tor Browser.</li><li>Create and implement a torspec proposal that uses Tor relays to increase your confidence that public logging actually happened when using Tor Browser.</li>
```
https://forum.torproject.net/t/privacy-preserving-and-incrementally-deployable-support-for-certificate-transparency-in-tor/953Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40032Old blog tag urls no longer reliably work2022-01-06T17:11:36ZRoger DingledineOld blog tag urls no longer reliably workDo a google search for 'dutch belgium law enforcement tor blog' and you'll find a link to <br>
https://blog.torproject.org/trip-report-tor-trainings-dutch-and-belgian-police/ <br>
(which works)
but you'll also find a link to <br>
https:...Do a google search for 'dutch belgium law enforcement tor blog' and you'll find a link to <br>
https://blog.torproject.org/trip-report-tor-trainings-dutch-and-belgian-police/ <br>
(which works)
but you'll also find a link to <br>
https://blog.torproject.org/category/tags/law-enforcement <br>
(which is a 404)
I guess this is related to that ticket a while ago where we made a list of blog tags we wanted to keep and we discarded all the others?
Is the new plan that we just pretend the old ones didn't exist, and we wait for google and everybody else to forget about them too, and we accept that links to the old tags will be broken?Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://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/40028Add a 404 page2021-11-24T19:02:06ZJérôme Charaouilavamind@torproject.orgAdd a 404 pageCurrently, the HTTP 404 page is the default one from Apache. We can probably whip up a nicer looking one.Currently, the HTTP 404 page is the default one from Apache. We can probably whip up a nicer looking one.https://gitlab.torproject.org/tpo/web/blog/-/issues/40027Discourse is unable to replace the lead image in the embed topic with an inte...2022-05-24T23:29:09ZJérôme Charaouilavamind@torproject.orgDiscourse is unable to replace the lead image in the embed topic with an internal uploadCurrently, when the forum embed a blog post on the forum and creates a new topic, the lead image `<img>` tag is replaced with an internal upload (which we want). But this upload goes wrong somewhere and instead, a visible markdown fragme...Currently, when the forum embed a blog post on the forum and creates a new topic, the lead image `<img>` tag is replaced with an internal upload (which we want). But this upload goes wrong somewhere and instead, a visible markdown fragment similar to this appears in its place:
```
![](upload://5I9gkH7W5MiboevmjzfyMDYfrJD.png)
```
I reported this to the Discourse team and they're looking into it.
In the meantime I've applied a workaround by configuring the forum to [disable auto image downloads](https://forum.torproject.net/admin/site_settings/category/files?filter=disabled%20image) from `blog.torproject.net` which isn't ideal because PrivacyBadger block this as a cross-domain embed.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40026Improve navbar for small screens2022-05-04T23:35:38ZJérôme Charaouilavamind@torproject.orgImprove navbar for small screensThe links in the top navbar could be displayed using a CSS burger menu on small screens, as it was on Drupal.The links in the top navbar could be displayed using a CSS burger menu on small screens, as it was on Drupal.https://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/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.org