Just your normal everyday casual software dev. Nothing to see here.

People can share differing opinions without immediately being on the reverse side. Avoid looking at things as black and white. You can like both waffles and pancakes, just like you can hate both waffles and pancakes.

  • 0 Posts
  • 9 Comments
Joined 2 years ago
cake
Cake day: August 15th, 2023

help-circle
  • Honestly, he doesn’t need to, All he has to do is have Congress go into adjournment on the 10th day of the bill being in his hand. And then when he doesn’t sign it, it’s supposed to go back to Congress. However, if Congress is adjourned, the bill gets pocket vetoed without the ability to be brought up again.

    I’m partially expecting with how much support has changed so drastically that that’s what the current plan is. Just have Congress go into adjournment. It prevents the house from bringing it up again as the bill gets fully tossed if I understand it correctly

    although I guess that is under the statement that he can get the house to close again




  • Someone in another post showed a decent site that shows cloudflare dependency, so I threw the top 35 actives from observer into it. It’s honestly not as bad as I expected it would be, but it is concerning.

    Lemmy

    lemmy.world(Active Users: 14512): Cloudflare? Yes(dns,proxy,cname)

    sh.itjust.works(Active Users: 2509): Cloudflare? Yes(dns,proxy,cname)

    lemmy.ml(Active Users: 2087): Cloudflare? No

    lemmy.zip(Active Users: 1704): Cloudflare? Yes(dns,proxy,cname)

    lemmy.dbzer0.com(Active Users: 1444): Cloudflare? No

    lemmy.ca(Active Users: 1381): Cloudflare? Yes(dns,proxy,cname)

    lemmygrad.ml(Active Users: 972): Cloudflare? No

    lemmy.blahaj.zone(Active Users: 956): Cloudflare? No

    programming.dev(Active Users: 929): Cloudflare? Yes(dns,proxy,cname)

    discuss.tchncs.de(Active Users: 778): Cloudflare? No

    sopuli.xyz(Active Users: 596): Cloudflare? No

    slrpnk.net(Active Users: 371): Cloudflare? No

    infosec.pub(Active Users: 331): Cloudflare? No

    lemmy.today(Active Users: 314): Cloudflare? No

    midwest.social(Active Users: 307): Cloudflare? No

    reddthat.com(Active Users: 292): Cloudflare? Yes(dns,proxy,cname)

    feddit.nl(Active Users: 290): Cloudflare? No

    pawb.social(Active Users: 243): Cloudflare? Yes(dns,proxy,cname)

    forum.guncadindex.com(Active Users: 234): Cloudflare? No

    mander.xyz(Active Users: 194): Cloudflare? No

    lemmings.world(Active Users: 177): Cloudflare? No

    ani.social(Active Users: 173): Cloudflare? Yes(dns,proxy,cname)

    feddit.it(Active Users: 158): Cloudflare? No

    startrek.website(Active Users: 156): Cloudflare? No

    feddit.dk(Active Users: 151): Cloudflare? Yes(dns,cname)

    leminal.space(Active Users: 126): Cloudflare? Yes(dns,proxy,cname)

    ttrpg.network(Active Users: 125): Cloudflare? No

    szmer.info(Active Users: 116): Cloudflare? No

    lemmy.eco.br(Active Users: 99): Cloudflare? Yes(dns,proxy,cname)

    lemy.lol(Active Users: 97): Cloudflare? Yes(dns,cname)

    awful.systems(Active Users: 90): Cloudflare? No



  • Pika@sh.itjust.workstoSelfhosted@lemmy.worldPSA syncthing-fork has changed owners
    link
    fedilink
    English
    arrow-up
    26
    arrow-down
    1
    ·
    edit-2
    2 days ago

    this entire thing has made me really rethink whether I want to swap to the new repo or not.

    Why was there no communication about it. The gplay repo maintainer wasn’t informed of anything, no public notice to anyone was given, just a transfer of the repo and a status issue here explaining it.

    Obviously the act is genuine as they were able to keep the original keys but like, this entire system seemed really sketchy.

    I’m also not happy with the fact that it seems the first thing they added was removing checksums, but that might be a temp thing.

    I also just noticed that it looks like they removed the entire public key for it, which if they had the original private keys using the existing public keys shouldn’t be an issue right?


  • One of my drives crippled itself a few days back, not sure what caused it. Wasn’t able to be resolved without a host restart which was unfortunate. SMART isn’t failing and has been working fine, so I’m chalking it down to a weird Proxmox bug or something.

    For sure expected I was going to need to do a rollback on an entire drive after that restart though. Still may have to if it reoccurs.