Search
690 results for “leafless”
-
Feeling for all those negotiators on the #australia #eu #FTA #freetradeagreement #aueufta...
-
-
@lmorchard #nilaypatel ,👏👏. It's tiring to watch the same corporate/tech lines about free speech, building things that might break and listening to our users...
-
@angusm @ct_bergstrom @cstross
If only #contractual languag could be this unambiguous. Note well, #lawyers #lawfedi -
Spare a thought for the #inhouse #lawyers trying to work out how to implement #auslaw #Australia social media ban... #grumpylawyer
-
Adobe to update vague AI terms after users threaten to cancel subscriptions | Ars Technica
-
Kindly stop 'hoping that I'm well'.
My welfare is generally not the concern of my correspondents. If the missive, to which these well wishes relate, is likely to decrease my welfare, then consider apologies instead.
#monday #inhouse #grumpylawyer -
"We track the Internet browsing behavior of 48,154 monthly visitors to the Web sites of 90 online software companies to study the extent to which potential buyers access the end-user license agreement. We find that only one or two of every 1,000 retail software shoppers access the license agreement"
https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1443256
WILD. And I'm guessing the 1-2 per 1000 are bored #lawyers #inhouse....
-
Sigh... sloppy lawyering and drafting of #termsandconditions deserves to be corrected so publicly. Wdyt #lawfedi #inhouse?
After overreaching TOS angers users, cloud provider Vultr backs off | Ars Technica
-
https://missing.csail.mit.edu/
"Classes teach you all about advanced topics within CS, from operating systems to machine learning, but there’s one critical subject that’s rarely covered, and is instead left to students to figure out on their own: proficiency with their tools."Does any one know if there's an equivalent for #lawyers? #LawFedi #lawprofs #inhouse
-
Looking forward to #thebezzle by @pluralistic!
Avoid all that #drm tosh and support it on https://www.kickstarter.com/projects/doctorow/the-bezzle-a-martin-hench-audiobook-amazon-wont-sell
-
@angusm @ct_bergstrom @cstross
If only #contractual languag could be this unambiguous. Note well, #lawyers #lawfedi -
@angusm @ct_bergstrom @cstross
If only #contractual languag could be this unambiguous. Note well, #lawyers #lawfedi -
@angusm @ct_bergstrom @cstross
If only #contractual languag could be this unambiguous. Note well, #lawyers #lawfedi -
@angusm @ct_bergstrom @cstross
If only #contractual languag could be this unambiguous. Note well, #lawyers #lawfedi -
Y-axis done, #Prusai3MK3S and Haribo time. Listening to Plastikman (www.youtube.com/watch?v=BWK6HXu3tg8)
-
PSA for weary #lawstudents #lawprof. If you're working with a word limit, make sure you've correctly toggled #word's word count
-
Doing it Righter
I had a draft of an article of how to do cookie-based advertising “right”, but third-party cookies are no more, so that one landed in the wastebasket.
How About Micropayments?
Tim Berners-Lee apparently said that his big error in designing the World Wide Web was to assume it would eventually be supported by advertising, instead of micropayments.
To be precise, he recently said
“Two myths currently limit our collective imagination: the myth that advertising is the only possible business model for online companies, and the myth that it’s too late to change the way platforms operate.”
Companies do on-line advertising auctions in ~120 milliseconds. If they can do that, and get the billing right, they can do micropayments.
How Would That Work?
Let’s assume I run a payments processor. One of my customers is a paywalled site called The Bookworm’s Den, and they want to charge 1/10 of a cent per page. They receive a GET request from a member, and immediately send a request to me, the payment processor.
I need to do three things, not all at the same time:
- Hash the customer’s ID into a table. If it’s not there, the customer of Bookworm’s Den doesn’t support micropayments. That’s bizarre, as they’re a member of the Bookworm’s Den. If it happens, though, I return “402 Payment Required” to the Bookworm. If the customer does do micropayments, I return “200 OK” and cache the table entry for subsequent page reads.
- Get my internal payment-id for the customer from the table, say 5280. Send a “subtract 0.001 from customer 5280, for bookworm” message to
- the cache, and
- the back-end database.
- A subtract doesn’t have to arrive in any order, it can sit in a queue if the database is busy, and it can even be saved on the http server for a while if the DB is down. If everything crashes, the Bookworm loses $0.001, the customer gets a freebie of $0.001, and I scramble madly to get things working again, because I only get paid if the Bookworm gets paid.
- Once a month, I scan the database for all users who have at least one subtract. I bill them, credit the sellers and set the user’s balance back to zero.
Sending subtracts with an amount makes the operations time-insensitive. Adding a date/time stamp makes them idempotent. The big risk to me is the database going down without the http server noticing, or of it going down and staying down.
Business Stuff
Mind you, I also need to have a relationship with the various credit- and debit-card companies and at least a few banks. I need to collect from one and pay the other. That’s pretty easy in Canada: we have five big banks and three big credit-card companies.
My customers, like the Bookworm’s Den, need to have a membership agreement with their users, so they have billing information for them, an agreement with the bank where I’ll be depositing their revenue and an agreement with me that I’ll be their agent.
That’s not everything, but it is sufficient. The hard part is getting started, as micropayments are a chicken-and-egg problem. If you don’t have them, you can’t offer them to your customers. If you don’t offer them to your customers, my micropayments company won’t have any money, and will probably go broke before it can pay for itself. And that will discourage the next micropayments company.
-
Doing it Righter
I had a draft of an article of how to do cookie-based advertising “right”, but third-party cookies are no more, so that one landed in the wastebasket.
How About Micropayments?
Tim Berners-Lee apparently said that his big error in designing the World Wide Web was to assume it would eventually be supported by advertising, instead of micropayments.
To be precise, he recently said
“Two myths currently limit our collective imagination: the myth that advertising is the only possible business model for online companies, and the myth that it’s too late to change the way platforms operate.”
Companies do on-line advertising auctions in ~120 milliseconds. If they can do that, and get the billing right, they can do micropayments.
How Would That Work?
Let’s assume I run a payments processor. One of my customers is a paywalled site called The Bookworm’s Den, and they want to charge 1/10 of a cent per page. They receive a GET request from a member, and immediately send a request to me, the payment processor.
I need to do three things, not all at the same time:
- Hash the customer’s ID into a table. If it’s not there, the customer of Bookworm’s Den doesn’t support micropayments. That’s bizarre, as they’re a member of the Bookworm’s Den. If it happens, though, I return “402 Payment Required” to the Bookworm. If the customer does do micropayments, I return “200 OK” and cache the table entry for subsequent page reads.
- Get my internal payment-id for the customer from the table, say 5280. Send a “subtract 0.001 from customer 5280, for bookworm” message to
- the cache, and
- the back-end database.
- A subtract doesn’t have to arrive in any order, it can sit in a queue if the database is busy, and it can even be saved on the http server for a while if the DB is down. If everything crashes, the Bookworm loses $0.001, the customer gets a freebie of $0.001, and I scramble madly to get things working again, because I only get paid if the Bookworm gets paid.
- Once a month, I scan the database for all users who have at least one subtract. I bill them, credit the sellers and set the user’s balance back to zero.
Sending subtracts with an amount makes the operations time-insensitive. Adding a date/time stamp makes them idempotent. The big risk to me is the database going down without the http server noticing, or of it going down and staying down.
Business Stuff
Mind you, I also need to have a relationship with the various credit- and debit-card companies and at least a few banks. I need to collect from one and pay the other. That’s pretty easy in Canada: we have five big banks and three big credit-card companies.
My customers, like the Bookworm’s Den, need to have a membership agreement with their users, so they have billing information for them, an agreement with the bank where I’ll be depositing their revenue and an agreement with me that I’ll be their agent.
That’s not everything, but it is sufficient. The hard part is getting started, as micropayments are a chicken-and-egg problem. If you don’t have them, you can’t offer them to your customers. If you don’t offer them to your customers, my micropayments company won’t have any money, and will probably go broke before it can pay for itself. And that will discourage the next micropayments company.
-
Doing it Righter
I had a draft of an article of how to do cookie-based advertising “right”, but third-party cookies are no more, so that one landed in the wastebasket.
How About Micropayments?
Tim Berners-Lee apparently said that his big error in designing the World Wide Web was to assume it would eventually be supported by advertising, instead of micropayments.
To be precise, he recently said
“Two myths currently limit our collective imagination: the myth that advertising is the only possible business model for online companies, and the myth that it’s too late to change the way platforms operate.”
Companies do on-line advertising auctions in ~120 milliseconds. If they can do that, and get the billing right, they can do micropayments.
How Would That Work?
Let’s assume I run a payments processor. One of my customers is a paywalled site called The Bookworm’s Den, and they want to charge 1/10 of a cent per page. They receive a GET request from a member, and immediately send a request to me, the payment processor.
I need to do three things, not all at the same time:
- Hash the customer’s ID into a table. If it’s not there, the customer of Bookworm’s Den doesn’t support micropayments. That’s bizarre, as they’re a member of the Bookworm’s Den. If it happens, though, I return “402 Payment Required” to the Bookworm. If the customer does do micropayments, I return “200 OK” and cache the table entry for subsequent page reads.
- Get my internal payment-id for the customer from the table, say 5280. Send a “subtract 0.001 from customer 5280, for bookworm” message to
- the cache, and
- the back-end database.
- A subtract doesn’t have to arrive in any order, it can sit in a queue if the database is busy, and it can even be saved on the http server for a while if the DB is down. If everything crashes, the Bookworm loses $0.001, the customer gets a freebie of $0.001, and I scramble madly to get things working again, because I only get paid if the Bookworm gets paid.
- Once a month, I scan the database for all users who have at least one subtract. I bill them, credit the sellers and set the user’s balance back to zero.
Sending subtracts with an amount makes the operations time-insensitive. Adding a date/time stamp makes them idempotent. The big risk to me is the database going down without the http server noticing, or of it going down and staying down.
Business Stuff
Mind you, I also need to have a relationship with the various credit- and debit-card companies and at least a few banks. I need to collect from one and pay the other. That’s pretty easy in Canada: we have five big banks and three big credit-card companies.
My customers, like the Bookworm’s Den, need to have a membership agreement with their users, so they have billing information for them, an agreement with the bank where I’ll be depositing their revenue and an agreement with me that I’ll be their agent.
That’s not everything, but it is sufficient. The hard part is getting started, as micropayments are a chicken-and-egg problem. If you don’t have them, you can’t offer them to your customers. If you don’t offer them to your customers, my micropayments company won’t have any money, and will probably go broke before it can pay for itself. And that will discourage the next micropayments company.
-
Doing it Righter
I had a draft of an article of how to do cookie-based advertising “right”, but third-party cookies are no more, so that one landed in the wastebasket.
How About Micropayments?
Tim Berners-Lee apparently said that his big error in designing the World Wide Web was to assume it would eventually be supported by advertising, instead of micropayments.
To be precise, he recently said
“Two myths currently limit our collective imagination: the myth that advertising is the only possible business model for online companies, and the myth that it’s too late to change the way platforms operate.”
Companies do on-line advertising auctions in ~120 milliseconds. If they can do that, and get the billing right, they can do micropayments.
How Would That Work?
Let’s assume I run a payments processor. One of my customers is a paywalled site called The Bookworm’s Den, and they want to charge 1/10 of a cent per page. They receive a GET request from a member, and immediately send a request to me, the payment processor.
I need to do three things, not all at the same time:
- Hash the customer’s ID into a table. If it’s not there, the customer of Bookworm’s Den doesn’t support micropayments. That’s bizarre, as they’re a member of the Bookworm’s Den. If it happens, though, I return “402 Payment Required” to the Bookworm. If the customer does do micropayments, I return “200 OK” and cache the table entry for subsequent page reads.
- Get my internal payment-id for the customer from the table, say 5280. Send a “subtract 0.001 from customer 5280, for bookworm” message to
- the cache, and
- the back-end database.
- A subtract doesn’t have to arrive in any order, it can sit in a queue if the database is busy, and it can even be saved on the http server for a while if the DB is down. If everything crashes, the Bookworm loses $0.001, the customer gets a freebie of $0.001, and I scramble madly to get things working again, because I only get paid if the Bookworm gets paid.
- Once a month, I scan the database for all users who have at least one subtract. I bill them, credit the sellers and set the user’s balance back to zero.
Sending subtracts with an amount makes the operations time-insensitive. Adding a date/time stamp makes them idempotent. The big risk to me is the database going down without the http server noticing, or of it going down and staying down.
Business Stuff
Mind you, I also need to have a relationship with the various credit- and debit-card companies and at least a few banks. I need to collect from one and pay the other. That’s pretty easy in Canada: we have five big banks and three big credit-card companies.
My customers, like the Bookworm’s Den, need to have a membership agreement with their users, so they have billing information for them, an agreement with the bank where I’ll be depositing their revenue and an agreement with me that I’ll be their agent.
That’s not everything, but it is sufficient. The hard part is getting started, as micropayments are a chicken-and-egg problem. If you don’t have them, you can’t offer them to your customers. If you don’t offer them to your customers, my micropayments company won’t have any money, and will probably go broke before it can pay for itself. And that will discourage the next micropayments company.
-
Doing it Righter
I had a draft of an article of how to do cookie-based advertising “right”, but third-party cookies are no more, so that one landed in the wastebasket.
How About Micropayments?
Tim Berners-Lee apparently said that his big error in designing the World Wide Web was to assume it would eventually be supported by advertising, instead of micropayments.
To be precise, he recently said
“Two myths currently limit our collective imagination: the myth that advertising is the only possible business model for online companies, and the myth that it’s too late to change the way platforms operate.”
Companies do on-line advertising auctions in ~120 milliseconds. If they can do that, and get the billing right, they can do micropayments.
How Would That Work?
Let’s assume I run a payments processor. One of my customers is a paywalled site called The Bookworm’s Den, and they want to charge 1/10 of a cent per page. They receive a GET request from a member, and immediately send a request to me, the payment processor.
I need to do three things, not all at the same time:
- Hash the customer’s ID into a table. If it’s not there, the customer of Bookworm’s Den doesn’t support micropayments. That’s bizarre, as they’re a member of the Bookworm’s Den. If it happens, though, I return “402 Payment Required” to the Bookworm. If the customer does do micropayments, I return “200 OK” and cache the table entry for subsequent page reads.
- Get my internal payment-id for the customer from the table, say 5280. Send a “subtract 0.001 from customer 5280, for bookworm” message to
- the cache, and
- the back-end database.
- A subtract doesn’t have to arrive in any order, it can sit in a queue if the database is busy, and it can even be saved on the http server for a while if the DB is down. If everything crashes, the Bookworm loses $0.001, the customer gets a freebie of $0.001, and I scramble madly to get things working again, because I only get paid if the Bookworm gets paid.
- Once a month, I scan the database for all users who have at least one subtract. I bill them, credit the sellers and set the user’s balance back to zero.
Sending subtracts with an amount makes the operations time-insensitive. Adding a date/time stamp makes them idempotent. The big risk to me is the database going down without the http server noticing, or of it going down and staying down.
Business Stuff
Mind you, I also need to have a relationship with the various credit- and debit-card companies and at least a few banks. I need to collect from one and pay the other. That’s pretty easy in Canada: we have five big banks and three big credit-card companies.
My customers, like the Bookworm’s Den, need to have a membership agreement with their users, so they have billing information for them, an agreement with the bank where I’ll be depositing their revenue and an agreement with me that I’ll be their agent.
That’s not everything, but it is sufficient. The hard part is getting started, as micropayments are a chicken-and-egg problem. If you don’t have them, you can’t offer them to your customers. If you don’t offer them to your customers, my micropayments company won’t have any money, and will probably go broke before it can pay for itself. And that will discourage the next micropayments company.
-
"The company says the new terms aren’t a change in how Mozilla uses data, but are rather meant to formalize its relationship with the user, by clearly stating what users are agreeing to when they use #Firefox "
This makes little #legal sense. The existing #termsandconditions are not any less 'formal'. This is just a line trotted out by a stressed legal and PR team (individuals have my sympathy; management less so). #LawFedi