[-] CameronDev@programming.dev 1 points 4 days ago

Yeah, there would be a lot of potential for leaks, but if they are one-time-codes that wouldn't be too bad.

[-] CameronDev@programming.dev 1 points 5 days ago

I've had the same though re. shipping addresses, but I don't think it scales well. You'd need every postie to have an online device that allows them to link QR code/uuid code to the real address, and delivery just gets a lot harder.

In Australia, AusPost allows you to generate a "virtual" PO box, which is a lot easier to deal with, but you have to go to the post office to pickup.

[-] CameronDev@programming.dev 2 points 5 days ago

Your website is dead.

[-] CameronDev@programming.dev 3 points 6 days ago

Thats how it works in theory, but in practice it comes down to trust more than anything else.

Its more effort to read and validate your list than it is to just go and download the installer directly. So you need people to trust you.

[-] CameronDev@programming.dev 1 points 6 days ago

Hello! Let us hold hands and wiggle them to greet each.

[-] CameronDev@programming.dev 3 points 6 days ago

Updating the gist gives a new URL no?

[-] CameronDev@programming.dev 1 points 6 days ago

Those tariffs would likely have eaten their entire margin so they have to pass it on. Even Panic had to pass them on.

Perhaps they could have gambled on the tariffs being rolled back, but if they got it wrong they would have lost money.

Its just a no-win scenario unless you can predict the future.

[-] CameronDev@programming.dev 1 points 6 days ago

Good for them. Are they selling direct to customers though? If yes, they have all the customer and payment details already, so it would be relatively easy?

[-] CameronDev@programming.dev 4 points 6 days ago

Your bot needs a little love, the screenshot has an overlay in it.

[-] CameronDev@programming.dev 2 points 6 days ago

Has any company given back the tariffs?

It honestly sounds like such a huge hassle to try give that money back. The amount of labor required would be huge, you'd need to check every receipt, probably manually. Make sure all of them are legit, aren't double submitted

[-] CameronDev@programming.dev 1 points 6 days ago* (last edited 6 days ago)

Its just reading the commit history. It doesnt read the files at all. So it only finds overt slop, anyone who does their commits manually would pass completely.

Edit: https://slopscore.ava.pet/repo/https%3A%2F%2Fgithub%2Ecom%2Fcameroncros%2Fedgy%2Dtable

This repo is 100% slop (its mine, I know what I did), and it gets marked clean.

[-] CameronDev@programming.dev 2 points 6 days ago

GitHub issues, wikis, forums, pastebins, comments, package metadata, social networks, public documents, deliberately agent-oriented services, etc. could all become pieces of shared external memory.

always has been meme

Thats exactly what all of those sites are, and always were - shared external memory. They were designed for humans to share knowledge amongst their peers. LLMs are trained off human behaviour (or at least a facsimile), so that they use the services similarly isnt surprising.

18

Day 22: Monkey Market

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

7

Day 21: Keypad Conundrum

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

11

Day 20: Race Condition

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

8

Day 19 - Linen Layout

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

6

Day 18: Ram Run

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

10
8

Day 17: Chronospatial Computer

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

7

Day 16: Reindeer Maze

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

11

Day 15: Warehouse Woes

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

15
submitted 2 years ago* (last edited 2 years ago) by CameronDev@programming.dev to c/advent_of_code@programming.dev

Day 14: Restroom Redoubt

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

18

Day 13: Claw Contraption

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

15

Day 12: Garden Groups

Megathread guidelines

  • Keep top level comments as only solutions, if you want to say something other than a solution put it in a new post. (replies to comments can be whatever)
  • You can send code in code blocks by using three backticks, the code, and then three backticks or use something such as https://topaz.github.io/paste/ if you prefer sending it through a URL

FAQ

view more: โ€น prev next โ€บ

CameronDev

0 post score
0 comment score
joined 3 years ago
MODERATOR OF