TehPers

I don’t disagree, but that wasn’t my point. Everyone has access to SMS messaging. Not everyone has an internet-based messaging app, and those who do are split among several different services.

Of course it doesn’t, I even called that out :)

EU is the European Union, a group of countries in Europe that share common laws with each other.

A channel where a dude works full time and YouTube is a side gig wouldn’t buy a $250k sound chamber to measure how loud the fans are on a crappy prebuilt (GN - the people who made the initial video about LTT). There are significant benefits to being full time dedicated to creating this content, and being paid well in response. Something like this would only be possible following your model if they already made tons of money outside of YT, in which case, they’re already rich so what’s stopping them from going full time doing what they want anyway and uploading those videos?

From what I understand, they’re removing all recommendations from the home page if you have watch history turned off, likely because they can’t give you any decent recommendations without data to recommend from. All you’d see is the search bar.

Personally, I think this is a great change. Default YT home screen has some of the worst recommendations I’ve ever seen, and if I’m telling them not to track my watch history, I probably don’t want to see whatever content they’re promoting to the average user either.

Aside from needing a phone, I really don’t see the issue with SMS. For sending quick messages to people directly, is there really a better tool? You (most likely) already have a phone plan, you already have a phone, and your phone is always on you. Everyone you’re trying to contact is in the same boat, even people who are technically illiterate. All phones with phone plans support SMS, unless there’s weird plans I don’t know about.

When it comes to more complex needs (group management, e2e encryption, etc) other services are better of course. I don’t use SMS to text my group of friends, it’s really not well suited for the job.

Probably something like this.

Odd, my google search just has a bunch of Lemmy/Mastodon results. Surely I’m doing something wrong, do I need to disable SafeSearch?

Donations don’t generate nearly as much money as purchases. I like open source just as much as the next person, but there’s no way that I could afford to drop my job and go full time into an open source project. Looking at Lemmy’s donations for example, the annual budget on OpenCollective is, at this time, ~$10k (which is significantly below US minimum wage at least), and their Patreon link shows $1650/mo. It’s a nice chunk of cash, but not sustainable.

One approach I’ve really liked is what Aseprite does. You can buy the precompiled product, or you can clone the repository and build it yourself. Most users won’t build it, so they get paid and still get to share the code with the community.

anyone who has an ounce of intelligence can easily parse this information in a few seconds regardless of its format.

1/4/2023

yyyy/mm/dd makes the most sense in my opinion and is the order used in ISO 8601 and similar specs (though in the format yyyy-mm-dd), but we already have enough culture-specific stuff that date formats are the least of our issues.

It’s only invalid if it generated errors.

I understand this line of thinking, but unless they specify what “flavor” of JSON they accept, I think it’s safe to assume they only accept what’s in spec. What I find weird is that they immediately contradict the spec with their example by writing JavaScript. Should the content-type then be application/javascript? They can easily document the parameters outside the request body instead of adding comments.

Also, yes, I know I’m being pedantic, but if I’m applying for a job, it’s a two way application. They need to give me reason to trust that they’re worth working for. Making up rules along the way when referencing a commonly known spec doesn’t give me much confidence.

Is it just me, or does their sample request use invalid JSON? The keys should be in quotes, comments aren’t in spec (but commonly supported), and trailing commas are invalid as well (but commonly supported).