Rewinding the video by double tapping left or skipping ahead by double tapping right, enabling subtitles, watching in 2x speed, full screen, toggling back and forth without losing your place in the video.
You get no ads but everything else sucks. I haven’t tried sibling’s suggestion for vinegar though, I’m taking about stock with a dns blocker.
all those things work perfectly for me in the browser . Occasioally if you double tap too fast it doesn't like it. but 2x speed, subs. toggling, dbl taps. all work great in safari on ios. I often have 2 or 3 videos that i watch over the course of a few days. I just leave them in tabs and come back to them as i get time. can't do that with the app.
So the works of J.R.R. Tolkien, who died in 1973, will enter the public domain in New Zealand (and other countries) next year? Or do they not, as he presumably published his works in the UK? Or they enter the public domain in New Zealand et al. but not in other countries?
So can they host the Gutenberg project in NZ then? There is no feasible way for people to prevent people from downloading the hobbit. They couldn't stop music or movie downloads except by adopting a subscription model that effectively reduced the prices. These files are tiny and the ethical case against it is so much harder to make.
Edit: also, these are the sorts of books that don't get lumped into subscriptions and are often missing from digital libraries.
> So can they host the Gutenberg project in NZ then?
There is already an Australian branch of Project Gutenberg, which hosts some works which (for complex/obscure legal reasons) are still under copyright in the US but now public domain in Australia (e.g. the works of George Orwell). I don’t think there is a New Zealand equivalent, but I’m sure if someone was sufficiently motivated it could happen
They can, but they'd have to make those downloads only available to NZ users. This is also why American sites need to block EU users or comply with the GDPR. You can't just pick a server location with the laxest laws.
IIRC, Gutenberg already does this, limiting access from Germany which has a stricter copyright than the US.
No, there is no requirement under US law to preemptively block non-US users, or under NZ law to block non-NZ users. German courts held that there was jurisdiction over PG because they had content in German, and PG decided to comply. But you can, in fact, pick a server location with lax laws. But you may be susceptible to get sued elsewhere (in some cases), and the local country can force ISPs to block your site, too, if you don't respond.
There's none. But the validity of a copyright of a work is dependent on the place in which you're applying the law, not on the place where the author is from (except when applying the rule of the shorter term).
Tons of works are in the public domain in one country, but not another.
The oldest still in effect copyright I know of is from 1611: the King James translation of the bible is still copyright of the crown in the UK. No other country recognizes that copyright.
> The oldest still in effect copyright I know of is from 1611.
I can beat that by over 4000 years.
As far as Icelandic copyright law is concerned the copyright on the
Diary of Merer[1], written 4500 years ago, will be held by the French Egyptologist Pierre Tallet until 2039.
This is because the copyright protection commerces when the work is made available for sale, loaning out etc. to the public.
If you discover a previously unpublished work that's not protected by copyright you get to enjoy 25 years of copyright protection, i.e. the copyright is assigned to the person who discovered and published the work.
I only have a source in Icelandic, it's article 44 of the copyright act [2].
The 25-year rule is part of an EU copyright directive (which Iceland, as an EEA country, has adopted as well). Also, this isn't technically a copyright, but an equivalent right. (And the right is not 4000 years old.) The EU directive says (in English):
> Any person who, after the expiry of copyright protection, for the first time lawfully publishes or lawfully communicates to the public a previously unpublished work, shall benefit from a protection equivalent to the economic rights of the author. The term of protection of such rights shall be 25 years from the time when the work was first lawfully published or lawfully communicated to the public.
The KJV is protected in the UK by Royal Prerogative rather than by copyright law. The KJV rights are actually older than copyright in the UK.
A number of countries have copyright restrictions on things of national significance, etc., however, and then there's the concept of domaine public payant.
Linux kernel development happens on Git. In fact, Git was created for the Linux kernel. Maybe instead of Git you mean GitHub? I can't find a link now, but if I remember right there was a brief period when Linux kernel development had to move to GitHub. Maybe when kernel.org got hacked? Linus Torvalds didn't like the way that GitHub formatted merge commits [1] (from a later date, but I think it was the same issue).
Yeah, github Web UI tend to generate low quality commit message that's not up to the standard set by the kernel developers: no oneline short log, long lines, no signed-off line, etc. Linus simply refuses to let those kind of commits into the Kernel.
Without involving github at all, you can use git directly to push branches to a remote repository and then have it be merged by the maintainers there, which leads to a workflow that's pretty similar to the one you have with github.
Instead, Linux is being worked on by exporting the (git) patches and sharing them on a mailing list, effectively not using a significant feature of git and leading to a very different workflow than the one everyone else is using (github users and others alike), so I still find the question legitimate.
>> Instead, Linux is being worked on by exporting the (git) patches and sharing them on a mailing list
Once configured, you can send a series of patches to the mailing list with a single git command, and with just another command apply a series of patches from the mailing list. It's actually quite efficient.
I'm aware of that mirror. What I'm talking about in my comment is that there was a time when the development of the Linux kernel actually moved to GitHub, due to problems with the regular Linux kernel development infrastructure.
Isn't that the point of X-ray spectroscopy? As a layperson I don't know of any point in trying to "photograph" a single atom, but surely being able to do spectroscopy on a single atom is really useful.
It's quite clear to me that tech companies know that reneging on WFH will cause some employees to leave. I think that this is actually the entire point. You can do a soft layoff, without ever having to say the word layoff, and without ever getting "Tech company XYZ announces layoffs" headlines.
The problem, I think, is what kind of employees may leave. If it's the best of the cream, then the company is in trouble. And frankly, the best employees can allow themselves to say "I want to work from home. You don't allow? Then goodbye".
In my opinion, above a certain size, companies don't really care about employee quality all that much. So long as they meet the initial hire criteria it doesn't matter who's a 5x or 1x dev anymore. It's just one FTE anyway in the planning.
At this point the company has become a bullshit churning machine whose effectiveness is measured by its rate of churn. They milk cash cows that gained traction in decades past, while most new work is just part of the churn.
We had an example at our office several years ago where employee X was a great worker, nothing to say about that, that was having his own "working" rhythm (e.g., until late at night, mornings off, etc.), and was coming to the office only from time to time, just because the manager was really pushing hard, or for certain office events.
This spread and people started to ask - can I work from home?
-> only 1 day
Why? X does more than 1 day, and sometimes X is not available when I need.
... as a manager you can only "yes, but ..." that much. At a certain point people (who I would like to remind everyone again and again: most of the time are people with a high college degree, used to read books, papers, and do things, not 3 years old kids) connect the dots and say "alright, it's time to go". And before they go, they let the entire apple tree rot to hell. If that doesn't happen it might be because this spreads and goes to high management that asks the manager "WTF are you doing?"
That's when either more rights come in equally for everyone, or ... they need to let go of their best employee, or they need to find a compromise. Just having the nicely protected "best" employee is never a good strategy. Eventually people get pissed off and leave, and if they don't, congrats, you have just made the "non-best" employees even less motivated and less productive.
This was so before COVID. If you are good and productive you can often negotiate WFH like any other benefit.
Honestly it seems like it’s part of a tech career trajectory. Once you are very established and your skills are built up there are several tracks available to you. Two of those are WFH specialist or 5-10X experienced dev and WFH consultant.
The cube farm grind is something you go through to get your skills and network up.
I have seen the same in other knowledge areas: corporate law, finance, some types of editing and design, accounting, etc. WFH becomes one of the options at more senior levels.
The other reason it’s a more senior option is that senior people are seen as better able to self direct and thus requiring less micromanagement.
That seems to be true in my case, the first decade of my career was spent in cube farms and cramped offices. I learned a lot and made a few networks, and now I’m at a fortunate point where most jobs are available to me with a phone call if my current job sucks. Especiallly when I’m asked to RTO.
Pre-covid my entire team was office and I was the only remote. Without wanting to brag, it's factual: my Drupal knowledge made it worth for them to keep this up. Post-covid my entire team is scattered to the winds. You couldn't get them to come to the office because almost no one is within the same metro as the office.
They are going to quickly discover that this is the case. I left Lockheed right after they started forcing everyone back into offices that didn't even have enough desks. Those whom were actually creating value there all had plans to leave to. Plenty of them left as soon as they got the news lol. Sure it's a way to do layoffs without saying 'layoff', but the impact is going to be felt much harder down the line.
I'm not sure that there is a terrible large correlation between "best of the best" and "refuse to ever work in office." When I think about the engineers that I most respect and admire, they are very split on wfh vs wfo opinions.
I don't think this is correct. It is a little hard to tease out perfectly (e.g.: school computers having gone to chrome books in a big way might not be the statistic you want), but globally Windows marketshare has gone from 90% a decade ago to ~%75 now:
I'm not a part of this space personally so I can't say for certain, but one answer could be the not-PCs and cloud. Some people find a tablet with a keyboard perfectly adequate for their all-office needs. Even if the "sys-admins" still need PCs that is still a very substantial conversion of the market share away from PCs. If you reflexively scream at the notion of how horrible that would be for your working process, I do not blame you but note it could work for some.
Do you really need to be part of “this space” to know that Microsoft has a 90% share in PCs and most of corporate America and even personal computers are running Windows?
Even the people who like tablets are still buying Surface laptops - running Windows.
They aren’t buying iPads and definitely not Android tablets.
Even a lot of iPad aficionados are moving back to Macs now that they have a lot of the advantages of iPads - slim, lightweight and ridiculously long battery life.
Nokia at one point started handing out very generous severance packages to get people out. The management thought that the bad workers would be the ones to take the deal.
Nope, the oldest and most experienced ones took the money and used it to start their own companies.
(As I always point out...) This is known as the "Dead Sea Effect" and it was traditionally associated with companies like IBM but now we're seeing it across the board with tech layoffs. The best people know they have options and they have a good network so once a company starts showing signs of slowing down they bail out.
Those headlines are usually associated with a bump in the stock price; it's unclear why they'd be trying to avoid them. Perhaps they think it undermines future hiring or retention, but so does RTO.
It can be bad optics for companies which took large sums of money from the government recently (say, for pandemic relief or major tax breaks of some kind) to then turn around and announce large layoffs. It guarantees that the CEO is going to have an unpleasant day or two in front of, say, a Congressional committee or maybe a state legislature hearing. And letting CEO's avoid unpleasant consequences of their own decisions is definitely an important factor in corporate decisions.
It's situational - sometimes a layoff headline may push your stock price down.
I imagine current round[0] of layoffs is opportunistic - companies know they'll want to do some layoffs at some point, but when's a better moment than when everyone else is doing layoffs? The public at this point doesn't even care anymore - there's been too much of it going on, it's not novel, it's what everyone's doing.
--
[0] - I'm not sure if "round" is even a good term anymore - it's been what, half a year already, of ongoing layoffs in tech companies? I've been seeing at least one headline per week about some recognizable name in tech announcing/executing layoffs, since February, or maybe even January 2023.
The problem is they are leaking talent, as those who know that can pick another offer that suits their needs will do without thinking about it too much.
I’m beginning to think so as well. You can get significant layoffs without having a “layoff” event, and you don’t have to provide any of the support that is required when firing people.
It’s clearly not what an employment lawyer would call “constructive dismissal” but it sure feels like that is the intent.
Sorry I'm habitually talking about us employment law that is generally as anti-worker as it is possible to be while still pretending that employees have rights.
It's also I realize kind of iffy. If Dell said explicitly "we will not ever require RTO", and you moved following that, then maybe your lawyer would be willing to bring a case, but in this case Dell is saying "if you live within an hour" you have to come in to the office. Given my employer's RTO has given me 3+ hours of commuting a day that seems in the region of what the US considers reasonable.
“Live within an hour” is interesting for Dell, given where their office is. At peak commute times this barely even covers north Austin, but off leash likely covers the entire metro area.
oh yeah - my mandatory RTO means I now need to drive for 2.5-4 hours a day.
Previously I could commute via public transit + work on commute buses, but given the lack of masking, vaccination requirements, or separation, driving is now the only safe option.
Not just for covid either: not going to the office meant I did not get sick for years - within a month of RTO starting I had one coworker saying that they would have been in the office but the (at the time) rules said you couldn't come to the office if you had flu symptoms even if you hadn't tested positive for covid. e.g. The only reason a coworker didn't come in while knowing that they work sick was because at the time it was explicitly prohibited.
If it’s in your contract then yes but if you were hired to work in an office but allowed to WFH for some time because of company policy I doubt it would be seen as such even in the UK
People are still acting like the current job environment doesn’t suck. Where are these trustworthy companies currently that aren’t also announcing layoffs or that you can count on not to have layoffs?
I don't think you can count of any company not to have layoffs, that's quite dependant on the economy, company performance, sector, etc.
If a company promised no layoffs ever, I wouldn't believe them. But if they promised to continue WFH, I'd believe them, since that's directly under their control.
Most employment is from small businesses, by the numbers. Most small businesses are struggling-to-fragile at best as most fail. The "not paying for office space is a sizable plus" contingent alone would give a substantial number of WFH jobs Counterintuitively there are loads of jobs from the companies who are struggling.
So many allow WFH. There's thousands of open software positions in SF alone, and plenty are ok with remote. Some are even ok with me being in the taiwan time zone. I'm managed to stay consistently employed in the Taiwan time zone with SF and NYC based jobs the last 2.5 years.
Curiously, for some candidates, almost every letter of the FAANG, WILL give a full WFH offer, today, and they are willing to put this down with ink on paper.
If you scroll down on the article in the OP, you'll see that Cantonese readings of Chinese characters are also context-specific, and they appear to have solved that problem with ligatures.
Eh, if it's my actual core team, like the devs I work with on a day-to-day, then it sounds cool. We haven't yet managed to replace that sense of free flowing adhocness that comes with being in an office together.
Yep I think we fail to articulate this well in the site. Flowy is a place for you and your core team (typically 3-8 people that are absolutely critical). The 20% of folks that you spend 80% of your time with, to focus and execute with.
That term is like the truck nuts of the software development world. Maybe they are consciously trying to filter out anyone serious. Kind of like why Nigerian Prince scams are so bad.
Gah, I just Googled "truck nuts". I thought it was something to do with wheel nuts. I was sadly mistaken. Why would people put that on their own vehicle?
