heimchen

I have an old PRS-T3 from Sony and would like to upgrade, but don’t know much about the current world of ereaders, maybe someone could help me. (The PRS is working fine for books, so I can wait, but many websites stopped working and I would like to upgrade)

It would have to be robust and have a similar form factor(maybe smaller but not much bigger)[3 inches/7.5 cm] and I would like physical buttons, but they are not required. Since I am using omnivore as a read it later app and read my local newspaper on these devices, google play and a webbrowser would help a lot.

Thanks.

I don’t need an integrated store or drm reader, I add all my books manually.

I would like to benchmark my rustcode with criterion, but the information it presents to me do not match up. Here is some of the output I get

Benchmarking big/big decoding: Warming up for 1.0000 s
Warning: Unable to complete 10 samples in 5.0s. You may wish to increase target time to 306.4s.
big/big decoding    	time:   [632.40 ns 724.40 ns 899.80 ns]
                    	change: [+0.7649% +16.645% +46.889%] (p = 0.04 < 0.05)
                    	Change within noise threshold.
Found 2 outliers among 10 measurements (20.00%)
  1 (10.00%) high mild
  1 (10.00%) high severe

If it took a criterion only 724.40 ns to run the code, why couldn’t it run the code 10 times in 5 seconds. I looked at the outliers in the browser and the one outlier took 1.5 microseconds to run so this could not be the problem.

I currently would record with obs, but this requires to stop at the right time and my mouse cursor is visible at the beginning. Do you have some tips for recording?

I am using liftoff on Android

It would really be nice if you could get to the post and comment which replied to your comment or post.

I heard it was possible, with BiglyBT bridges, but I never used BiglyBT and can't get it to work.

I have

• working i2p proxy
• BiglyBT installed with i2p helper

I would have no problem with command line commands

I was looking for a way to use a reverse Proxy with my nextcloud snap install, this guid was what I needed. https://github.com/nextcloud-snap/nextcloud-snap/wiki/Putting-the-snap-behind-a-reverse-proxy

First change, what ports nextcloud listens to: sudo snap set nextcloud ports.http=81 ports.https=444

Install haproxy and append this to the config file in /etc/haproxy/haproxy.cfg

backend nextcloud-http                                                                                                                                                                                                                        
        mode http                                                                                                      
        balance roundrobin                                                                                                                                                                                                                    
        option forwardfor                                  
        option httpchk HEAD /
        http-check send ver HTTP/1.1 hdr Host localhost
        server nextcloud 127.0.0.1:81 check                                                                            
        timeout connect 4s                                 
        timeout server 4s                 
                                                           
backend nextcloud-https                                    
        mode tcp                                                                                                       
        balance roundrobin
        option httpchk HEAD /                                                                                                                                                                                                                 
        http-check send ver HTTP/1.1 hdr Host localhost                                                                                                                                                                                       
        option ssl-hello-chk                   
        server nextcloud 127.0.0.1:444 check                                                                                                                                                                                                  
        timeout connect 4s                                                                                             
        timeout server 4s      

And this for the front end, don't forget to change to your domain. nextcloud.example.org

frontend http                                                                                                          
        bind *:80                                                                                                      
        mode http                                                                                                                                                                                                                             
                                                                                                                                                                                                                                              
        acl host_nextcloud hdr(host) -i <domain name>                                                                  
        use_backend nextcloud-http if host_nextcloud       
        timeout client 4s                                                                                              
                                                                                                                       
frontend https                                             
        bind *:443                                         
        mode tcp                                                                                                       
                                                                                                                       
        tcp-request inspect-delay 5s                       
        tcp-request content accept if { req_ssl_hello_type 1 }
                                                                                                                       
        acl host_nextcloud req_ssl_sni -i <domain name>                                                                
        use_backend nextcloud-https if host_nextcloud                                                                  
        timeout client 4s

Check if everything is correct with sudo haproxy -c -f /etc/haproxy/haproxy.cfg and start it.

sudo systemctl enable haproxy
sudo systemctl start haproxy

just do the lets-encrypt stuff again: nextcloud.enable-https And it worked for me(Apache)

Do you use the default location for the database? I found a cool middle ground that allowed me to run my operating system and snap off a ssd and the database on a slower hdd.
I installed nextcloud with snap and did the setup.
When everything was how I wanted it to be, I search for the datas location
(for me:/var/snap/nextcloud/common/nextcloud/data). Then I created a /data on my hdd and binded it to nextclouds /data folder.
My fstab now looks like this:
/data /var/snap/nextcloud/common/nextcloud/data none bind 0 0
You only have to rebuild the database:

nextcloud.occ files:cleanup
nextcloud.occ files:scan

!!! Important, move your data first to the new location.(I think you won't lose it, but you cannot access it)

I just installed stable diffusion on my homelab and did not change anything, but the outputs are really bad, I tried following tutorials, but my version just outputs really weird stuff.

What am I doing wrong?

I would like to host a small instance for me and my friends (<10). I was thinking about buying a small single board arm computer to host it. What would be the minimum system requirements for this and do you have recommendations besides the raspberry pi.