Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)IN
Posts
1
Comments
522
Joined
3 yr. ago

  • I also read that there's some rule chaneges (on what is considered yes/no) by polymark on some bets and general complaints, don't know if those are just sore losers or valid but I'd read up on that if you want to bet on the platform, I've never used the service.

  • Anyone can dispute a proposed market resolution if they feel it was proposed in error. Once a market is proposed for resolution it goes into a challenge period of 2 hours. If no one challenges the proposal the resolution is deemed valid and the proposer receives their bond back plus the reward. During the 2-hour challenge period, anyone may dispute the proposal on the UMA dapp by posting a challenge bond of the same amount as the proposer bond (usually $750). This begins the debate period of 24-48 hours (votes happen every other day and there will always be at least 24 hours for discussion). Anyone wishing to contribute evidence to the discussion can do so in the Uma Discord server in the #evidence-rationale and #voting-discussion channels. After the debate period, Uma token holders vote (this process takes approximately 48 hours)

    https://docs.polymarket.com/polymarket-learn/markets/how-are-markets-resolved

    https://docs.polymarket.com/polymarket-learn/markets/dispute

  • Here:

     
        
    server {
        listen 443 quic;
        listen [::]:443 quic;
        listen 443 ssl;
        listen [::]:443 ssl;
        server_name jellyfin.kitsuna.net;
        http2      on;
        http3      on;
        quic_gso   on;
        tcp_nodelay on;
        # You can increase the limit if your need to.
        error_log /var/log/nginx/jellyfin.access.log;
    #    ssl on;
    #    ssl_certificate /etc/nginx/certificate.crt;
    #    ssl_certificate_key /etc/nginx/certificate.key;
    #    ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # don’t use SSLv3 ref: POODLE
            ssl_certificate /etc/letsencrypt/live/kitsuna.net/fullchain.pem;
            ssl_certificate_key /etc/letsencrypt/live/kitsuna.net/privkey.pem;
    #        ssl_certificate_key /etc/letsencrypt/live/kitsuna.net/privkey.pem;
            ssl_protocols TLSv1.2 TLSv1.3;
            add_header Alt-Svc 'h3=":$server_port"; ma=86400';
            add_header x-quic 'h3';
            add_header Alt-Svc 'h3-29=":$server_port"';
        location / {
            proxy_pass http://10.159.4.12:8096/;
    #       proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
            proxy_set_header Host $http_host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forward-Proto http;
            proxy_set_header X-Nginx-Proxy true;
        }
    }
    
      
  • They're creating their mod list, fixing bugs, add mods they forgot, re-ordered the mod list and have to wait 10 minutes for the game to even load after each change. And in the end they don't even play the finished modpack.

  • Selfhosted @lemmy.world

    Kubernetes storage backends