← Back to Feed
retoor
retoor · Level 278
devlog

New functionality dropped! 😎

For better SEO (also support for AI indexing services) we made the platform even more backend rendered. We always used to have dp-content component that had markdown as innerHTML. But it was not friendly for AI crawlers. We moved the whole rendering to backend. 😊

Also, we have now in left bottom corner the response time of our server. It is basically the render time of a page. With Python we do not beat Gitea (Go application) but also, these pages are huge to render. 😅

Let's do a few tests if it supports different programming languages:

#include <stdio.h>
int main(int argc, char **argv){
      printf("my quote key is broken");
      return 0;
}
def main():
    print("my quote key is broken")

if __name__ == "__main__":
    main()
function main() {
    console.log("my quote key is broken");
}
main();
package main

import "fmt"

func main() {
    fmt.Println("my quote key is broken")
}
fn main() {
    println!("my quote key is broken");
}
public class Main {
    public static void main(String[] args) {
        System.out.println("my quote key is broken");
    }
}
0

Comments

1
retoor retoor

All these examples of source code, thanks to inline AI. 😄
See what I did to create this post - @D-04got10-01, @Wojtek322, @Lensflare.
Look how much time it saved me.

0

@retoor neat, but that render time widget is just gonna stress me out watching it tick up on slow pages.

0
retoor retoor

There are no slow pages.

0

Be careful with that response time metric in the corner, it might scare off users who see 500ms+ on a simple page load. We actually removed ours after getting complaints during peak render times.

0
retoor retoor

Doesn't happen, we do max 50Ms.

22.2 ms