The comparison table available here has a concern, when scrolling over the columns, you don't know what the rows correspond to anymore.

The first column with the feature names should be always visible on the left side.

When I cloned a fresh copy of that repo, I got this warning from git-lfs:

> git clone [email protected]:berty/www.berty.tech.git
Cloning into 'www.berty.tech'...
remote: Enumerating objects: 137, done.
remote: Counting objects: 100% (137/137), done.
remote: Compressing objects: 100% (123/123), done.
remote: Total 1269 (delta 29), reused 52 (delta 11), pack-reused 1132
Receiving objects: 100% (1269/1269), 17.98 MiB | 126.00 KiB/s, done.
Resolving deltas: 100% (186/186), done.
Filtering content: 100% (299/299), 322.51 MiB | 3.86 MiB/s, done.
Encountered 1 file(s) that should have been pointers, but weren't:
	bertytech/content/newsletter/news-23/giphy.gif

Elements using the amp-script such as the navbar and FAQ accordion are messed up. Reason is the classList methods "add" "remove" and "toggle" do not output the class.

Odd thing is that this only happens using the CDN (latest version) and not when using the local AMP JS files.

As @Jorropo suggested, we can now add the crowdin link (http://berty.crowdin.com/) instead of 'cooming soon' on the contribute page (https://berty.tech/fr/contribute).

@cdeleeuwe can you handle it?

Thanks :)

Based on berty/community#108

We need to fix few elements:

• While download link is not available, display by a GitHub link to Berty repo on homepage.
• Display somewhere else our comparison table between Berty and other apps (https://berty.tech/faq#what-are-the-advantages-of-berty-compared-to-the-other-messengers)

@cdeleeuwe can you handle it?

• Change all internal links to .RelLangPermalink
• Add fallback for blog posts

Fallback options are:

1. Duplicate blog post to French, but be sure to have two things:

• canonical URL pointing to the English URL
• lang==en, even if there is /fr/ in the URL

2. If English article is not translated, link to it from the french version, but not with /fr/ in the URL

Please feel free to open PRs to help us fix typos and other content issues 🙏

While trying to fix #4 I'm not able to build (berty{tech,art}/) :

$USER@$HOSTNAME:~/Documents/Scripts/www.berty.tech/bertytech$ ./pre-build.sh 
$USER@$HOSTNAME:~/Documents/Scripts/www.berty.tech/bertytech$ make dev
hugo server -D -F --disableFastRender --bind=0.0.0.0 --baseURL=/ --appendPort=false
Building sites … ERROR 2020/09/03 23:36:36 failed to render pages: render of "page" failed: execute of template failed: template: _default/single.html:2:3: executing "_default/single.html" at <partial "head" .>: error calling partial: "/home/$USER/Documents/Scripts/www.berty.tech/bertytech/layouts/partials/head.html:98:38": execute of template failed: template: partials/head.html:98:38: executing "partials/head.html" at <$style.Content>: error calling Content: TOCSS: failed to transform "bundle.scss" (text/x-scss): resource "scss/bundle.scss_66c51675248977a80b16bae70957083e" not found in file cache
Built in 930 ms
Error: Error building site: TOCSS: failed to transform "bundle.scss" (text/x-scss): resource "scss/bundle.scss_66c51675248977a80b16bae70957083e" not found in file cache
make: *** [Makefile:8: dev] Error 255
$USER@$HOSTNAME:~/Documents/Scripts/www.berty.tech/bertytech$ hugo version
Hugo Static Site Generator v0.74.3-DA0437B4 linux/amd64 BuildDate: 2020-07-23T16:22:34Z

It seems like netlify is grabing the file from his cache instead of building it.
Did I miss something in the build process ?

This is a suggestion and a request for comment for the matrix comparison

1. is there a specific reason I'm not aware of for which the open source value was left blank?
2. based on these latest developments I think we should at some point consider changing their distributed tab to partially or wait for the implementation to be final to change it to true?
3. consider e2ee is now default in 2-participant rooms, but yes this does not change the status to true
4. why is the aosp tab void? does riot / riotx android client not work without GCM?

I think this is important as IMO Matrix [along with signal] is the real leader on the bleeding edge out there, and is investing a lot in P2P, so it'd be interesting to cross-reference approaches and advantages/disadvantages with them. Shoutout to Jami and status.im of course.

Thanks!

@cdeleeuwe :

Can you add a button underneath the project section (https://berty.tech/docs#projects) that link to the community page?

Feel free to adjust the style of the button to fit the page.

Depends on #3

There is a black line on the homepage (see below)

I am on Mac & Chrome and I have this awful line just above "The latest articles on the blog" at the bottom of the homepage. I don't know if it's just me.

@cdeleeuwe can you fix it?

Change how AMP JS libs are loading as discussed in #32 (comment)

@cdeleeuwe can you add the last modified time on this page (https://berty.tech/docs/protocol)?

Like a timestamp on the top of the page.

Thanks @D4ryl00 for the idea.

The idea is to keep the good practices that come with google AMP, but remove the trigger that forces to be 100% consistent + that says to google “hey, you can AMPize my website in your cache”

So, if I’m not wrong, just remove the ⚡ from the HTML head, but it needs to be double-checked

Clearly, I don’t like being in the Google cache system, and I don’t like having warning because of the limitations introduced by AMP, but it’s by far, my current favorite good practice handbook in term of performances, and organization

hint: pretty sure that there are blogposts explaining how other people made the same thing

Hi @cdeleeuwe,

Currently on the home page of the site at "Built for
the distributed web" there is an illustration that needs to be changed. Our graphic designer has been working on it. (see below the illustration).

She also worked on an animated version. We're afraid that the loading time of the page will be too long. Can you give us your advice?

Can you integrate his changes? The output files are either in GIF, MP4, H264, and JSON.

If so, I will ask her the correct output version.

Many thanks :)

Animated version: https://trello-attachments.s3.amazonaws.com/5e5fa5e4549cce7e3d595cc3/5e5fae6cc887ee21c5d0d5d7/014b8e1d033b4a39872e224a25a1727b/2020-03-09-Berty-illu-IPFS-homepage-site-anim-Exemple-implantation.mp4

Here's the Weekly Digest for berty/www.berty.tech:

ISSUES

Last week 7 issues were created.
Of these, 5 issues have been closed and 2 issues are still open.

OPEN ISSUES

💚 #109 Cleaning / correction of the comparison table, by aeddi
💚 #103 Matrix.org comparison not updated, by nordurljosahvida

CLOSED ISSUES

❤️ #108 feat(blog): create gomobile-ipfs blogpost, by pierreboc
❤️ #107 chore(blog):modify covers, by pierreboc
❤️ #106 feat(blog): create dao blogpost, by pierreboc
❤️ #105 Remove matrix, by cdeleeuwe
❤️ #104 Remove Matrix, by Camillesjoholm

LIKED ISSUE

👍 #108 feat(blog): create gomobile-ipfs blogpost, by pierreboc
It received 👍 x1, 😄 x0, 🎉 x0 and ❤️ x0.

NOISY ISSUE

🔈 #106 feat(blog): create dao blogpost, by pierreboc
It received 2 comments.

PULL REQUESTS

Last week, 4 pull requests were created, updated or merged.

MERGED PULL REQUEST

Last week, 4 pull requests were merged.
💜 #108 feat(blog): create gomobile-ipfs blogpost, by pierreboc
💜 #107 chore(blog):modify covers, by pierreboc
💜 #106 feat(blog): create dao blogpost, by pierreboc
💜 #105 Remove matrix, by cdeleeuwe

COMMITS

Last week there were 13 commits.
🛠️ Update index.md Signed-off-by: pierreboc [email protected] by pierreboc
🛠️ Merge pull request #107 from berty/dev/pierre/fix chore(blog):modify covers by moul
🛠️ Merge pull request #108 from berty/dev/pierre/gomobile feat(blog): create gomobile-ipfs blogpost by pierreboc
🛠️ chore: Add gfanton author by cdeleeuwe
🛠️ feat(blog): create gomobile-ipfs blogpost by pierreboc
🛠️ chore(blog):modify covers by pierreboc
🛠️ Merge pull request #106 from berty/dev/pierre/dao feat(blog): create dao blogpost by pierreboc
🛠️ Update index.md Signed-off-by: pierreboc [email protected] by pierreboc
🛠️ chore: make .Params.author case insensitive by cdeleeuwe
🛠️ chore: Add PhilH author by cdeleeuwe
🛠️ feat(blog): create dao blogpost by pierreboc
🛠️ Merge pull request #105 from berty/dev/cas/remove_matrix Remove matrix by moul
🛠️ chore: remove matrix by cdeleeuwe

CONTRIBUTORS

Last week there were 3 contributors.
👤 pierreboc
👤 moul
👤 cdeleeuwe

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository berty/www.berty.tech to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

It happens when the author contains the first + last name.

@cdeleeuwe can you handle this?

Thx :-)

Based on this comment, some AMP checkers are complaining: #25 (comment)

@cdeleeuwe can you give a look please?

Their website: https://coy.im/

after merging the last crowdin PR #248; the website was broken, but netlify didn't detect it as broken; it was released but without homepage

we should ensure that a partially built website is not published; do not hesitate to use a dummy method like counting the amount of generated HTML files

I thought we could add a "support" page that would centralize our support information. It could be easier for the application to be registered in stores.

I've already asked Ombéline, our graphic designer, to prepare 3 illustrations (attached).

It would need 3 parts with buttons to the different pages:

• FAQ (https://berty.tech/faq) and the image of the books
• Community (https://berty.community/) and the image of the house
• Contact (https://berty.tech/contact) and the image of the old phone.

@cdeleeuwe can you handle it?

We have decided stop using Matrix and mainly focus our communications on Discord.

And as always, you can contact Berty via email and follow us on Twitter @berty.

To contact Berty anonymously and securely, please follow the instructions on our Contact page.

Remove Matrix on the footer

Remove Matrix on the Contact page

https://berty.tech/contact

Remove Matrix on the Press page

https://berty.tech/press

Sometimes the amp-script isn't triggered and the obfuscated email address isn't showing. For example on the FAQ page sometimes it shows as..

Don't know if this is intentional or required but the docs/press folder is included two times in the repository.

The paths:

./bertytech/static/docs/press/
./bertytech/assets/docs/press/

While trying to automate the build process on my vps I got these error :

berty-build@vps644888:~/www.berty.tech/bertytech$ npm install
npm WARN [email protected] No description
npm WARN [email protected] No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 465 packages from 336 contributors and audited 468 packages in 16.223s

11 packages are looking for funding
  run `npm fund` for details

found 6 vulnerabilities (3 low, 3 high)
  run `npm audit fix` to fix them, or `npm audit` for details
berty-build@vps644888:~/www.berty.tech/bertytech$ make prod-build-ipfs
./pre-build.sh
BERTY_IPFS=true hugo --gc 
Building sites … ERROR 2020/09/05 15:08:00 render of "page" failed: execute of template failed: template: _default/single.html:2:3: executing "_default/single.html" at <partial "head" .>: error calling partial: "/home/berty-build/www.berty.tech/bertytech/layouts/partials/head.html:16:18": execute of template failed: template: partials/head.html:16:18: executing "partials/head.html" at <$image.Fill>: error calling Fill: image "/home/berty-build/www.berty.tech/bertytech/content/contact/berty_contact.png": fill : image: unknown format
ERROR 2020/09/05 15:08:00 render of "page" failed: execute of template failed: template: _default/single.html:2:3: executing "_default/single.html" at <partial "head" .>: error calling partial: "/home/berty-build/www.berty.tech/bertytech/layouts/partials/head.html:16:18": execute of template failed: template: partials/head.html:16:18: executing "partials/head.html" at <$image.Fill>: error calling Fill: image "/home/berty-build/www.berty.tech/bertytech/content/contribute/berty_contribute.png": fill : image: unknown format
ERROR 2020/09/05 15:08:00 render of "page" failed: execute of template failed: template: _default/single.html:2:3: executing "_default/single.html" at <partial "head" .>: error calling partial: "/home/berty-build/www.berty.tech/bertytech/layouts/partials/head.html:16:18": execute of template failed: template: partials/head.html:16:18: executing "partials/head.html" at <$image.Fill>: error calling Fill: image "/home/berty-build/www.berty.tech/bertytech/assets/img/berty_social.png": fill /img/berty_social.png: image: unknown format
ERROR 2020/09/05 15:08:00 render of "page" failed: execute of template failed: template: _default/single.html:2:3: executing "_default/single.html" at <partial "head" .>: error calling partial: "/home/berty-build/www.berty.tech/bertytech/layouts/partials/head.html:16:18": execute of template failed: template: partials/head.html:16:18: executing "partials/head.html" at <$image.Fill>: error calling Fill: image "/home/berty-build/www.berty.tech/bertytech/content/features/berty_features.png": fill : image: unknown format
Total in 6107 ms
Error: Error building site: failed to render pages: render of "page" failed: execute of template failed: template: _default/single.html:2:3: executing "_default/single.html" at <partial "head" .>: error calling partial: "/home/berty-build/www.berty.tech/bertytech/layouts/partials/head.html:16:18": execute of template failed: template: partials/head.html:16:18: executing "partials/head.html" at <$image.Fill>: error calling Fill: image "/home/berty-build/www.berty.tech/bertytech/content/about/berty_about.png": fill : image: unknown format
make: *** [Makefile:36: prod-build-ipfs] Error 255
berty-build@vps644888:~/www.berty.tech/bertytech$ hugo version
Hugo Static Site Generator v0.74.3-DA0437B4/extended linux/amd64 BuildDate: 2020-07-23T16:30:30Z
berty-build@vps644888:~/www.berty.tech/bertytech$ node
node    nodejs  
berty-build@vps644888:~/www.berty.tech/bertytech$ node --version
v11.15.0
berty-build@vps644888:~/www.berty.tech/bertytech$ npm --version
6.14.8

The version of hugo, npm, go and node are exactly the same as on my host machine where it's working fine, any build/dev doesn't work.

the site build&publish just failed because it timed out after >30min

can you update a little bit the timeout limit and see if you can improve the speed (it is mostly due to the i18n support which will probably be worse and worse over time -> more articles, more languages)

The second paragraph is a blockquote, the two around aren't

In the docs/berty site the shields are very big, taking up almost the entire screen.

We have few videos to share:

• https://www.youtube.com/watch?v=jtAtIsyUn0A (P2P FESTIVAL Antoine)
• https://www.youtube.com/watch?v=fnl7Omsbpbw (P2P FESTIVAL Manfred)
• https://www.youtube.com/watch?v=8el2hnjGCqg (ITW Manfred PP2P festival)
• https://www.youtube.com/watch?v=p2ZAm2fAvUo (IPFSCAMP)
• https://www.youtube.com/watch?v=YZJ5NXs8MUM (DAO)
• https://www.youtube.com/watch?v=jVT-tbkwqAw&list=PLuhRWgmPaHtToVYaDkd6ZTwB2Lo30s1vB&index=6 (UPDATES FROM BERTY IPFS)

IMHO best display section is in the docs section of the website (https://berty.tech/docs). A new square with a camera picto called "Videos".

if you land on https://berty.tech/blog/lkjsdflkjsdf or https://berty.tech/blog/lkjsdflkjsdf/, you will get a 404 page -> normal :)

but if you click on a link in the menu, it will generate another 404 link -> problem

At maintainers in the Readme the Berty staff team link is broken. I don't know if you want to fix this or have it removed but thought id let it know.

Configure the website to support i18n

• Configure Hugo
• Update .RelPermalink to RelLangPermalink
• Add alternate lang meta tags
• Add crowdin config
• Shortcodes
• Authors
• Dates
• Partials
• Footer
• Menu items
• About Page
• Blog Page (list & single)
• Challenges Page
• Apps compare table
• Contact Page
• Contribute Page
• Docs Page (list & single)
• Download Page
• FAQ Page
• Features Page
• Help Page
• Jobs Page (list & single)
• Newsletter Page (list & single)
• Press Page
• Privacy Policy Page
• Terms Page
• Home Page
• Easteregg Page
• Hello Page
• Id Page
• Fix relative assets paths with language prefix

• Connect crowdin.com
• initial french translation for the interface
• translate one of the blogposts

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository with URL https://x-access-token:[secure]@github.com/berty/www.berty.tech.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment and make sure the repositoryUrl is configured with a valid Git URL.

Good luck with your project ✨

Your semantic-release bot 📦🚀

That some boxes are empty seems ok as long as anyone can complete the table via a PR (even if some boxes are obvious like the purchase/runtime fee from Telegram or the privacy respecting terms of Weechat).
But for reasons of credibility, we must at least ensure that there is no obvious misinformation. For the same reasons we should correct typos / wrong naming and add sources that confound the veracity of a checkbox.

Global:

• end-to-end encryption -> End-to-End Encryption
• Skuttlebut -> Scuttlebutt
• Skred -> Skred (Twinme) or Twinme (Skred)
• Facebook -> Facebook Messenger (or at least Facebook M. if there are size constraints)
• Anonymous use possible -> What does that mean? Shouldn't we decline into Email required, Credit card required, etc...?
• We should have a tooltip that displays a description and links on each feature / checkbox.

Signal:

• No purchase fee == Partially -> ?
• No phone number required == True -> I don't think so.

Threema:

• Open Spec == False -> They have a whitepaper so it should at least be Partially.

Olvid: (changes reverted by error, adding them to the checklist as a reminder)

• No phone number required == False -> Wrong it's true.

Matrix:

• See #103

Here's the Weekly Digest for berty/www.berty.tech:

ISSUES

Last week 17 issues were created.
Of these, 15 issues have been closed and 2 issues are still open.

OPEN ISSUES

💚 #63 WIP change features page layout, by cdeleeuwe
💚 #57 Add Yolo on https://berty.tech/docs#projects, by moul

CLOSED ISSUES

❤️ #67 feat:create nl36, by pierreboc
❤️ #66 fix:change cover image, by pierreboc
❤️ #65 Change homepage IPFS animation, by cdeleeuwe
❤️ #64 fix: add more detail, by sfroment
❤️ #62 fix: typo in footer, by cdeleeuwe
❤️ #61 IPFS illustrations on Homepage, by pierreboc
❤️ #60 Add "Support our work" button, by cdeleeuwe
❤️ #59 Adding "support our work" button, by pierreboc
❤️ #58 Update covid-local-cooperation blogpost, by pierreboc
❤️ #56 Show last modified date on all docs, by cdeleeuwe
❤️ #55 Last Modified Time, by pierreboc
❤️ #54 fix: typos in post-fosdem-2020 blog article, by cdeleeuwe
❤️ #53 chore:adding video from FOSDEM, by pierreboc
❤️ #52 feat:create bp pp2p, by pierreboc
❤️ #50 Added missing quotation in challenges/constraints, by connertennery

LIKED ISSUE

👍 #64 fix: add more detail, by sfroment
It received 👍 x2, 😄 x0, 🎉 x0 and ❤️ x0.

NOISY ISSUE

🔈 #59 Adding "support our work" button, by pierreboc
It received 4 comments.

PULL REQUESTS

Last week, 14 pull requests were created, updated or merged.

UPDATED PULL REQUEST

Last week, 1 pull request was updated.
💛 #63 WIP change features page layout, by cdeleeuwe

MERGED PULL REQUEST

Last week, 13 pull requests were merged.
💜 #67 feat:create nl36, by pierreboc
💜 #66 fix:change cover image, by pierreboc
💜 #65 Change homepage IPFS animation, by cdeleeuwe
💜 #64 fix: add more detail, by sfroment
💜 #62 fix: typo in footer, by cdeleeuwe
💜 #60 Add "Support our work" button, by cdeleeuwe
💜 #58 Update covid-local-cooperation blogpost, by pierreboc
💜 #56 Show last modified date on all docs, by cdeleeuwe
💜 #54 fix: typos in post-fosdem-2020 blog article, by cdeleeuwe
💜 #53 chore:adding video from FOSDEM, by pierreboc
💜 #52 feat:create bp pp2p, by pierreboc
💜 #50 Added missing quotation in challenges/constraints, by connertennery
💜 #48 Corrected misspelling in goals/index.md, by connertennery

COMMITS

Last week there were 34 commits.
🛠️ Merge pull request #67 from berty/dev/pierre/nl36 feat:create nl36 by pierreboc
🛠️ feat:create nl36 by pierreboc
🛠️ Merge pull request #66 from berty/dev/pierre/fix2 by moul
🛠️ fix:change cover image by pierreboc
🛠️ Merge pull request #65 from berty/dev/cas/change_IPFS_homepage_image Change homepage IPFS animation by pierreboc
🛠️ Merge pull request #64 from sfroment/dev/sfroment/precision by moul
🛠️ chore: typo by moul
🛠️ fix: add more detail Signed-off-by: sacha-froment-ext [email protected] by sfroment
🛠️ chore: Change homepage IPFS animation by cdeleeuwe
🛠️ Merge pull request #62 from berty/dev/cas/fix-typo fix: typo in footer by moul
🛠️ fix: typo by cdeleeuwe
🛠️ Merge pull request #60 from berty/dev/cas/support-work-btn Add "Support our work" button by pierreboc
🛠️ feat: Improve hover effect by cdeleeuwe
🛠️ chore: move support our work btn to partial by cdeleeuwe
🛠️ chore: Swap icon and text by cdeleeuwe
🛠️ feat: Add support work button on doc single pages by cdeleeuwe
🛠️ feat: Add support our work button on blog by cdeleeuwe
🛠️ feat: Add "Support our work" button by cdeleeuwe
🛠️ Merge pull request #58 from berty/pierreboc-patch-1 by moul
🛠️ Update index.md by pierreboc
🛠️ Merge pull request #56 from berty/dev/cas/add-lastmodified-date Show last modified date on all docs by pierreboc
🛠️ feat: Show last modified date on all docs by cdeleeuwe
🛠️ Merge pull request #52 from berty/dev/pierre/bp-pp2p feat:create bp pp2p by moul
🛠️ Merge pull request #54 from berty/dev/cas/fix-typo fix: typos in post-fosdem-2020 blog article by moul
🛠️ fix: typos by cdeleeuwe
🛠️ Merge pull request #53 from berty/dev/pierre/fix1 chore:adding video from FOSDEM by moul
🛠️ fix: Change iframe to shortcode by cdeleeuwe
🛠️ chore: Add youtube shortcode by cdeleeuwe
🛠️ chore:adding video from FOSDEM by pierreboc
🛠️ update index.md Fix a typo in tags by pierreboc
🛠️ feat:create bp pp2p by pierreboc
🛠️ Merge pull request #48 from connertennery/patch-1 Corrected misspelling in goals/index.md by moul
🛠️ Merge pull request #50 from connertennery/patch-2 Added missing quotation in challenges/constraints by moul
🛠️ Added missing quotation in challenges/constraints It may be misplaced, but there's no beginning quotation to Making sure you are who you claim to be" by connertennery

CONTRIBUTORS

Last week there were 5 contributors.
👤 pierreboc
👤 moul
👤 sfroment
👤 cdeleeuwe
👤 connertennery

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository berty/www.berty.tech to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

There is a problem with the interpretation of the markdown on Berty's website compared to hackmd.

Example, for this markdown:
The signature of he Group ID ($G_{ID}$) and the member device ID public key ($D_P$) by the member ID secret key ($M_S$)

Berty's website render:

Hackmd render:

I don't know if it's possible to modify the markdown to make the syntax compatible with Hugo's interpreter (does it support this kind of rendering?).

@cdeleeuwe:

We now have a page for feature requests (https://vote.berty.community/). Can you link it from the support page (https://berty.tech/support)?

You can use this image:

Thanks :)

Here's the Weekly Digest for berty/www.berty.tech:

ISSUES

Last week 7 issues were created.
Of these, 6 issues have been closed and 1 issues are still open.

OPEN ISSUES

💚 #49 Setup a comment system, by moul

CLOSED ISSUES

❤️ #48 Corrected misspelling in goals/index.md, by connertennery
❤️ #47 fix line on homepage, by cdeleeuwe
❤️ #46 Fix this line (homepage), by pierreboc
❤️ #45 Change to Lanczos resample filter for blog images, by cdeleeuwe
❤️ #44 core:remplace cover image by new ones, by pierreboc
❤️ #43 feat: add UX/UI blogpost, by alexsland

LIKED ISSUE

👍 #43 feat: add UX/UI blogpost, by alexsland
It received 👍 x1, 😄 x0, 🎉 x1 and ❤️ x1.

NOISY ISSUE

🔈 #45 Change to Lanczos resample filter for blog images, by cdeleeuwe
It received 5 comments.

PULL REQUESTS

Last week, 7 pull requests were created, updated or merged.

MERGED PULL REQUEST

Last week, 7 pull requests were merged.
💜 #47 fix line on homepage, by cdeleeuwe
💜 #45 Change to Lanczos resample filter for blog images, by cdeleeuwe
💜 #44 core:remplace cover image by new ones, by pierreboc
💜 #43 feat: add UX/UI blogpost, by alexsland
💜 #42 Boutique link + text updated, Sponsors link, various grammar fixes, by nellyasher
💜 #35 adding the personas, by nellyasher
💜 #32 Some changes to prepare the website for IPFS, by fte378

COMMITS

Last week there were 18 commits.
🛠️ Corrected misspelling in goals/index.md "strengths" was misspelled as "strenghts" by connertennery
🛠️ Merge pull request #45 from berty/dev/cas/improve_blog_image_quality by moul
🛠️ Merge pull request #47 from berty/dev/cas/fix_line_on_hompage by moul
🛠️ fix: Change section-articles bg color by cdeleeuwe
🛠️ fix: line on homepage, fixes #46 by cdeleeuwe
🛠️ chore: increase timeout by cdeleeuwe
🛠️ chore: Upgrade Hugo to 0.69.2 by cdeleeuwe
🛠️ Update index.md by pierreboc
🛠️ Merge pull request #43 from alexsland/dev/alex/blogpost_ux_ui by moul
🛠️ chore ignore GIF resizing by cdeleeuwe
🛠️ chore: Change to Lanczos resample filter by cdeleeuwe
🛠️ Merge pull request #32 from fte378/fte_ipfs_preparation by moul
🛠️ Merge pull request #44 from berty/dev/pierre/cover1 by moul
🛠️ Merge pull request #35 from nellyasher/patch-4 by moul
🛠️ Update index.md by nellyasher
🛠️ core:remplace cover image by new ones by pierreboc
🛠️ feat: add UX/UI blogpost by alexsland
🛠️ Merge pull request #42 from nellyasher/patch-5 Boutique link + text updated, Sponsors link, various grammar fixes by pierreboc

CONTRIBUTORS

Last week there were 6 contributors.
👤 connertennery
👤 moul
👤 cdeleeuwe
👤 pierreboc
👤 nellyasher
👤 alexsland

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository berty/www.berty.tech to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

Here's the Weekly Digest for berty/www.berty.tech:

ISSUES

Last week 5 issues were created.
Of these, 3 issues have been closed and 2 issues are still open.

OPEN ISSUES

💚 #85 Initial comparison table, by cdeleeuwe
💚 #84 Update images on features page, by cdeleeuwe

CLOSED ISSUES

❤️ #86 feat:create nl38, by pierreboc
❤️ #83 added the mention of "no cloud" and peer-to-peer, by nellyasher
❤️ #82 Remove sitemap submission on postbuild, by cdeleeuwe

NOISY ISSUE

🔈 #82 Remove sitemap submission on postbuild, by cdeleeuwe
It received 2 comments.

PULL REQUESTS

Last week, 7 pull requests were created, updated or merged.

UPDATED PULL REQUEST

Last week, 2 pull requests were updated.
💛 #85 Initial comparison table, by cdeleeuwe
💛 #84 Update images on features page, by cdeleeuwe

MERGED PULL REQUEST

Last week, 5 pull requests were merged.
💜 #86 feat:create nl38, by pierreboc
💜 #83 added the mention of "no cloud" and peer-to-peer, by nellyasher
💜 #82 Remove sitemap submission on postbuild, by cdeleeuwe
💜 #81 chore: update index.md, by pierreboc
💜 #63 Change features page layout, by cdeleeuwe

COMMITS

Last week there were 20 commits.
🛠️ Merge pull request #86 from berty/dev/pierre/nl38b feat:create nl38 by pierreboc
🛠️ feat:create nl38 by pierreboc
🛠️ Merge pull request #82 from berty/dev/cas/remove-postbuild-submit-sitemap Remove sitemap submission on postbuild by moul
🛠️ chore: Add netlify plugins Signed-off-by: Cassius [email protected] by cdeleeuwe
🛠️ Merge pull request #83 from nellyasher/patch-6 added the mention of "no cloud" and peer-to-peer by moul
🛠️ added the mention of "no cloud" and peer-to-peer by nellyasher
🛠️ chore: remove sitemap submission on postbuild Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ Merge pull request #63 from berty/dev/cas/change-features-page-layout Change features page layout by cdeleeuwe
🛠️ fix: remove file pushed by accident Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ chore: update text & images Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ chore: reduce padding on featured sections Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ chore: add text highlighting Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ chore: cleanup TODO Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ chore: remove bottom padding on mobile Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ chore: Order on mobile Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ chore: minor improvements Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ feat: improve forms Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ chore: Change featured page (WIP) Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ chore: Change featured page (WIP) Signed-off-by: Cassius de Leeuwe [email protected] by cdeleeuwe
🛠️ Merge pull request #81 from berty/pierreboc-patch-2 chore: update index.md by moul

CONTRIBUTORS

Last week there were 4 contributors.
👤 pierreboc
👤 moul
👤 cdeleeuwe
👤 nellyasher

STARGAZERS

Last week there was 1 stargazer.
⭐ adhanot
You are the star! 🌟

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository berty/www.berty.tech to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆

See https://git-lfs.github.com/

I am curious to learn more about what is currently happening in Berty's ecosystem.

Since Hugo doesn't change the CSS assets to relative paths. A workaround might be something like:

{{ $segments := split (trim .RelPermalink "/") "/"}}
{{ $rel_path := apply $segments "print" ".." }}
{{ $rel_path = delimit $rel_path "/" }}
    
    <style>

      @font-face {
        font-family: 'Font Awesome 5 Pro';
        font-style: normal;
        font-weight: 400;
        font-display: swap;
        src: url("{{ $rel_path }}/fonts/fa-regular-400.eot");
        src: 
          url("{{ $rel_path }}/fonts/fa-regular-400.eot?#iefix") format("embedded-opentype"), 
          url("{{ $rel_path }}/fonts/fa-regular-400.woff2") format("woff2"), 
          url("{{ $rel_path }}/fonts/fa-regular-400.woff") format("woff"), 
          url("{{ $rel_path }}/fonts/fa-regular-400.ttf") format("truetype"), 
          url("{{ $rel_path }}/fonts/fa-regular-400.svg") format("svg"); }
</style>

The following CSS assets need to change:

• Slick font
• Fontawesome font
• Google Font