I don't understand why this isn't 'alright, pack it up and ship it and we'll send you a replacement'.
This should be a case of the engineering team getting the faulty device for debug (and ideally getting all the relevant information so they can do the work with some semblance of parity with the customer's setup) -- and the other half is the customer gets a functional piece of hardware to swap in.
If Framework is worried about sending out hardware before receiving hardware, the policy is a simple one; when we get the hardware, we'll ship your replacement.
---
and the amount of back and forth for the serial number of part X, then Y, then firmware of Z, etc.. maybe there's a technical reason for that but i just considered myself beat into submission and gave up.
This is the standard 'debug over the phone' thing and engineers will do this while collecting information to try and recreate the problem you're having. It may be because the engineers are too close to the process? If you think about it, the RMA process is actually a sales process. You're essentially selling an already sold user on continuing to be a user.
> I don't understand why this isn't 'alright, pack it up and ship it and we'll send you a replacement'.
Oh no. It should be "we have sent you a replacement - once it's installed and confirmed working, pack up the broken one and send us in the provided box with the provided pre-paid return label".
Best thing about Dell for example, with an enterprise contract you can overnight parts based on a machines service tag and they come with a prepaid return label, super easy and simple.
I'm fine with a middle ground - either run the support questions/tests and get the prepaid advance RMA, or say "I know what the fucking problem is, give me the advance RMA and bill me for shipping if the returned part is fine and I'm a dumbass."
In reality many people will NOT take the second option, but will be happy it was there, and the company probably never bothers billing for incorrect advance RMAs.
Exactly. Framework prides itself on its repairability, yet their support acts like any other PC manufacturer. If your stuff is so repairable, why can't I get billed the parts I know I need, and I can prove to you that this was necessary so you don't bill me?
It's cheaper in the short term to just ignore complicated support issues. As long as customer demand is high and orders are coming in, it's also a successful strategy.
For example Dyson is known to provide exceptional support for their vacuums. They often even replace damage for free that was clearly the user's fault. But their products are really expensive. Probably not much more expensive to manufacture than their competitor's products for half the price. They probably don't even lose money if they have to send a replacement once.
I've been experimenting with the same thing! Still don't have enough evidence to be able to say if it's beneficial or not, but hopefully will have a conclusion soon
https://github.com/comalice/pi-tools contains a 'memory everywhere' module that makes all sessions BM25 vectors, and surfaces a set of memory tools to enable agents to search. You can add a new machine to the mix by registering a 'spoke'. The app runs on the 'hub'. I want to containerize the core app soon.
You can also change which computer is the hub fairly easily.
This is a potentially reductive take, but, property tax is theft.
In the guise of 'paying your fair share to be a part of society', property tax is essentially the institution of serfdom to the royalty of state bureaucracy.
Property tax is effectively the same as rent, but the one collecting rent also has martial and lawfare capabilities. Not to mention effectively unlimited funds with which to crush anyone who doesn't fall in line.
If what you have can be taken by another if you don't meet some set of conditions, you don't really own that thing, do you? It's more like a loaner than it is 'I own this thing'.
---
I'll offer a blanket alternative for state and federal taxation: no taxes on individuals, their income, or their property. Instead we tax exchange. States levy a 10% VAT on all transactions. Federal government levies taxes on interstate commerce, imports, and exports only.
All other forms of taxation are barred. New taxes may not be levied. If the state needs additional funds it may issue short or long term bonds accordingly.
Money printing is shifted away from being owned by an international banker's consortium, re-pinned to durable goods or precious metals.
Yes that is generally what you get down to: you can’t really own land free and clear in a populated area. You depend on the government in many ways to enforce property rights, as well provide services for that property and in return you have to pay for that.
It makes me uncomfortable too actually but I can’t see any alternative that does not get back to a similar spot or violence. In addition if we shifted to a land value tax, it would push taxes onto the very dense developed areas encouraging better use.
This should be a case of the engineering team getting the faulty device for debug (and ideally getting all the relevant information so they can do the work with some semblance of parity with the customer's setup) -- and the other half is the customer gets a functional piece of hardware to swap in.
If Framework is worried about sending out hardware before receiving hardware, the policy is a simple one; when we get the hardware, we'll ship your replacement.
---
This is the standard 'debug over the phone' thing and engineers will do this while collecting information to try and recreate the problem you're having. It may be because the engineers are too close to the process? If you think about it, the RMA process is actually a sales process. You're essentially selling an already sold user on continuing to be a user.reply