stevecrox

The GPL requires you to distribute the GPL source code along side artefacts generated from it.

Red Hat used to share everything with everyone, they never needed to do that. To meet the requirements they need to share the code sources with licensed customers. This is what they have switched to doing.

This is my problem with the GPL, it feels like a cult of personality built around Stallman. With people assuming its somehow a magical license.

Businesses largely treat GPL as libraries they don't modify (or legal gets frowny face) so they don't have to share their code.

The "less free" licenses are generally ok to use and modify (the WTFPL caused fun with legal in one job). If you modify an open source project its normally easy to build a business case/convince a client to upstream the changes.

All the Red Hat changes demonstrate is another step towards an Oracle/Microsoft licensing model. Which is a good reason to not use RHEL or Fedora.

They have chosen to use a populist message.

So I assume they share the same traits as other populists. Populists never believe in the cause, only self enrichment.

They by design don't understand why things are structured and done the way they are because it undermines their simplistic message. "It would all be fixed if we just did x, or got rid of y"

They all seem to rely on culture wars "x group gets more than you, z are trying to stop, etc...).

So I assume if the council are using a populist message they have messed up and seeking to escape blame and maybe get something on the side.

I understand all of those words but not the sentence.

I know there are differences in sound replication quality, but the difference between high end and cheap kit has eroded over the last 10 years.

Its like comparing 720p to 1080p, sure there is a difference and 1080p is better, but not 10 times the cost improvement. 4k is having the same issues selling itself atm.

Thinking of Apple kit as Jewelry makes so much sense.

I have a pair of £40 Bluetooth earbuds and recently asked a group of co-workers why they owned Airpods.

They all admitted the sound quality was worse but it has a nifty find my airpod function. Which put me off buying Airpods.

Thinking of them as £200 earrings explains alot. The reason you buy them isn't for a practical purpose but to be seen in them or look pretty (which is entirely subjective).

Sounds like Orkney council aren't doing a very good job and are looking to distract from that e.g. "its not us, its Edinburgh/London!". The bit about the Shetland islands is telling.

Personally I suspect this investigation will result in a lot of 'fact finding' missions to Scandinavian countries, Isle of Jersey, etc.. for the council members and result in a quietly dropped report.

Change to subscribed
On KBin the default view is similar to /r/all this can be changed to limit your view to only magazines/communities you are subscribed to by going:

• Select your account name in top right corner
• Select 'Settings' from the account context menu
• Select 'Subscription' from the 'Homepage' drop down
• Select 'Save' on the settings page

This will change your default URL to https://<insance url>/sub (e.g. https://kbin.social/sub). This will change your feed to the top/newest/hottest from your subscribed magazines/communities.

Time Filter
If you look at the KBin screen, you will notice a filter by time option. Look for the navigation bar with hottest/newest/etc.. on it on that bar is a upwards arrow and 4 lines representing a triangle (its normally used as a sort symbol). That will let you set time limits similar to those mentioned in this post (e.g. 3 hours, 6 hours, 12 hours, 1 day, 1t (is 1 week).

Microblogs
Its also worth looking at the 'microblogs' feature under /sub as that will focus on mastodon messages/kbin microblogs with hashtags associated with your magazines/communities.

You can ask KBin to subscribe to people you find through Mastodon, due to the rate changes various twitter users are migrating around. I find KBin a nicer way to read their content.

I tried to self host using the docs and docker.

Normally I would check out source, build and deploy, but the docs suggest an entirely manual deployment or build/deploy via docker compose.

The issue I hit was figuring out what had failed in the process, I would have preferred a CI guide to produce working docker images and a CD guide for deploying the docker images.

The reason I gave up is there aren't any release markers, I tried with develop and main and couldn't figure out if it was me or the branches weren't in a buildable state.

I don't expect the a release to be perfect just an indicator that a working product was created at this point.

Its the way its reported.

A few years back there seemed to be a plethora of studies which were "Consuning <insert hot liquid> increases chance of throat cancer".

You would have to go to the source report (if lucky the bottom of the article) to find out it increased the risk by 0.1% - 0.5%.

When you factor in only 2,300 people in the UK (70 million) get throat cancer each year and the biggest risk factor was smoking and non smokers are pretty much within statistical error bars.

It makes the report uninteresting and only useful in a "someone already looked into this" way and yet a month would go buy and there would be a new article .. who knew chicken soup causes cancer...

This could be achieved within the UI and seems like a good idea.

Each kbin/lemmy instance decides to follow magazines/communities from others through activity pub and stores it locally for the instance.

Having the UI retrieve all local posts with the same magazine/community name (e.g. m/star_trek@kbin.social c/star_trek@lemmy.world). Wouldn't be hugely difficult, I believe Kbin uses postgres database as the local store. The community/instance should be columns you can search for, it would be a small SQL change.

Even if that wasn't an option, there is a means to get all of the magazines/communities from the kbin UI and retrieve all posts for a specific magazine/community. So you could do it entirely in a web client.

The combined view wouldn't change how you comment on specific posts. The issue is where do you post and what view would take dominance (e.g. if a magazine had themed itself).

The solution here would be to default to the local instance if it exists or the instance providing the most posts/comments. Perhaps with a drop downso users can choose.

Stable.

Its work, I don't care about the latest drivers or application releases. Just security updates

I will die onthis hill along with David Mitchell and could NOT care less what people think.

Most businesses IT departments I have worked for mandate a Linux distribution with a big support contract to deploy anything. The Windows System Admins think it will block adoption.

The businesses quickly realised that CentOS worked as a RHEL stand in and all developers can use that.

The logic of CentOS was it was identical to production and so minimised deployment issues but everything deploys in docker now.

As long as I have a Linux based docker host (cause the windows one has weirdness), I don't care what that host is, or how it is configured.

This now reflects in developer environment, I will write guides for Debian (because Snaps), devs can run whatever they want. I specify Ubuntu LTS for production since you can get a support contract for it.