Pika

From what I understand, those are not mutually exclusive clauses in this case. On first glance it seems trademark usage is defined as using it to your own power for your own purposes. Simply supplying the trademark as a form of attribution such as on a footer, attribution page or header isn’t generally trademark usage since it’s a requirement of the license itself.

What would be considered usage would be if they went a step further and claimed ownership or that they had control over said project. The easiest way of violating this seems to be if you do not supply your own branding at the same time, so their marking is the only marking on the page, this would deceive people into thinking you are the project, which would be in violation of trademark usage.

This is just what I found at first glance though, IANAL

It was a version of Ubuntu Server. I don’t know what one I think 2012?

No, I disagree.

It is not one person’s doing. That is the deflection.

I will not downplay the effect of this by saying they are the only one involved. Every maintainer so far that has locked or approved any changes that they did are equally at fault here. In fact, one of those linked articles even stated that the primary reason they locked it is because they didn’t like the amount of coverage it got. This is a failure on the community as a whole, not the individual.

edit for clarification: By failure, I’m talking more on projects that are humoring it and actually going through with it without considering the potential side effects of just blanket applying that.

Currently considering that a handful of these are locked or posted as we don’t know if we’re going to be doing this yet, I haven’t quite put them in that same sector yet, but it’s rapidly approaching it.

I’m not PC but, one benefit of using a central server for syncthing is an always on backup that doesn’t require another client device to be on, it also allows for easier creation of new shares.

For example, with syncthing you can set the “servers” client device to auto approve/accept any shares that are to trusted devices, then when you get a new device, instead of needing to add that device to every device you share on the syncthing network, you only need to add that device to the server and then you can have your other clients connect to the servers share instead of device to device. It’s easier. You can also configure the shares on the server to use encryption by default too, since you don’t really ever need to actually see the files on the server since it’s basically a install and forget style client.

As an example of what I mean:

I have 10 different devices that run syncthing, 9 clients and a “server” client. these clients are not always on at the same time, and as such when I change a file, the files can become desynced and cause issues with conflicts. By having a centralized server, as long as the server is on(it always is) and client itself is online, it’s going to always sync. I don’t need to worry about file conflicts between my clients as the server should always have the newest file.

Then for example say my phone died. Instead of needing to readd every seperate client that the phone needs to share with to the new device, I only need to add the phone as a trusted source on the “server” client via the webui -> click share to that device on every share the phone needs, and then remap the shares to the proper directories on the mobile device. this is vs having to add every device to the phone, and the phone to every device it needs access to ontop of reconfiguring all the shares. It’s simpler, but fair warning does cause a single point of failure if the server goes offline.

yea I have the machine backed up in case this happens. I have noticed that its a mess UI wise. But ipfire doesn’t seem to be stable. every few months it’ll randomly kill itself which will take everything on the network down until i manually restart the machine and then force tell it a new DNS server. It’s something I’ve never managed to resolve on the machine, and I don’t seem to have that issue with my test network with OPNsense.

I’m in the process of switching from ipfire to opnsense myself.

I hate how bloaty opnsense is at first glance but it has so much more control so once I copy my current config I’ll be leaving ipfire in the dust.

I have never thought of doing this. That’s now going on my server.

It’s not just new projects that are switching. I’m seeing an increasing amount of current projects that provide a way of upgrading to another thing like Postgres or MariaDB, Due to the lack of innovation and change on MySQL

Well this was a no brainer, I don’t know if anyone in the topic really believed game devs liked it, Executive and financing though? They love it.

But… “leadership and executive love DLSS 5” sounds worse than “Game Dev’s Love DLSS 5”.

The game devs position gives a false sense of security of “oh well maybe it isn’t actually a bad thing”… the other just sounds like cost saving.

I have a similar experience when I code while drinking.

I’ll come up with the most insane ways of doing it that surprisingly look really clean… but when I wake up in the morning it’s a “how did I even think of this and how does this work”

for a senior engineer position though? That seems counterproductive. I would expect it of one of the entry levels or non-it but forcing a windows ecosystem on a development or engineering sector screams red flag to me.

Not that this has ever stopped them before, but I would be interested on their attempt at remaining compliant with data protection laws as I feel like locking GDPR right to be forgotten behind a facial ID scan would be seen as an unneeded blocker in order to delete your account.

I’m all some Debian dereritive, whether it’s Q4OS or just Debian,

deleted by creator

I lack the use case for this service but, it looks good on paper. Nice!

If I understand the project right, this would be a great opening for non-profit communities to make a page for the town and add the services, instead of the typical static pages

That’s amazing to see, Regardless if it’s only one direction, that should still help wonders, thank you for the addition!

I definitely understand your reasonings for that. And I do agree having it default on does help raise awareness of communities.

My main reason that I’m against a default on is I’m always strongly against any type of action that does something on the behalf of someone else without it properly being relayed.

if the person who made the community wanted to advertise their community, they could reach out and send a message on their own, or they could turn it on, but having it default on creates cases like this, Where they weren’t even aware that it was making a post, it seems, until people started messaging them complaining about the amount of spam.

this would be an amazing addition! It would help avoid the disconnect between de-federated instances/communities

Basically many domain providers will hold onto domains for a little while after it expires.

Some like namecheap also advertise the domain names to peddle-man companies that will somehow buy temporary access to the domain after your extortion recall window expires.

To continue the namecheap example, when your namecheap domain expires, it gives you a lapse window where you can pay like double the cost of the domain renewal to reclaim it. If you don’t reclaim it during that window they give it to a middleman whom will somehow buy a 2 or 3 months domain lease for it. They will put it on a “site for sale” broker page and will charge you easily 100x what you paid for the domain if you wanted it back.

I would recommend just keep checking on it every few days to see if it gets released.

That sounds like a really dumb setting.

Like, I’m sure it’s helpful for people who want it. But, like, it definitely sounds like a setting that should be defaulted off, not defaulted on.