morras

@morras@links.hackliberty.org
1 Post – 16 Comments
Joined 11 months ago

Best distro: the one you are currently using on a daily basis.

Worst distro: windows

Cost-cutting is corporate-greed mindset, therefore you have to solve it with the same mindset.

Fire people ! Even you if needed. And let the end-users deal with the outcome.

(This is not a serious post ^^ )

2 more...

“The waters may be rough right now,” he wrote, “but there’s no other ship I’d rather be on, and no other crew I’d rather be with, as we weather this cycle and emerge even stronger on the other side.”

Sure, as you know that you can throw people overboard to save your own ass.

First, you need a use-case. It's worthless to have a server just for the sake of it.

For example, you may want to replace google photos by a local save of your photos.

Or you may want to share your movies accross the home network. Or be able to access important documents from any device at home, without hosting them on any kind of cloud storage

Or run a bunch of automation at home.

TL;DR choose a service you use and would like to replace by something more private.

Even though, only the winning side would draft the "official" version of the events. The "real" "truth" would appear only decades later, when everyone involved is dead (or almost) and independant research can happen. E.g. a former French "résistant" recently confessed his group summarily executed a bunch of captured German Soldier in 1944. Some of the members went in politics afterwards, preventing any investigation to take place.

In France there are some mistakes that became social markers.

People following conspiracy theories are mostly bad educated people, and they wrongly conjugate some verbs.

The most common examples are:

  • "Nous sachons", instead of "Nous savons" (we know)
  • "Ils croivent" instead of "Ils croient" (they think, they believe)
  • "Comme même" instead of "Quand même" (nonetheless, despite, kinda hard to translate)

Making one of those mistakes will immediately tag you as a fool.

1 more...

The EDPS open-sourced a cookie inspection tool:

https://edps.europa.eu/edps-inspection-software_en

1 more...

He has actually a point. You need access to your services for which purposes? As long as you are @home, you have access to your services (but those cannot reach outside). You can still browse your photos and likes.

If you are out, it's easier to get a copy of what you need on your device (e.g. passwords) than set up a backup internet connection. (IMO, at least)

And if your client (or client's insurance) is just half-way competent, they will notice that some stuff have no activated license.

You will end up in a world of pain.

Just don't do that.

3 more...

Not dealing with **the effects of **copyright is the thing here.

And in that sense he can gain some insights ;)

If I had to implement this business model, I would go to a country that don't give a f* about dcma & stuff, and implement it in a similar way as Mega did.

With just the adjunction that if you upload a new book, you get free subscription for one week/month/year (depending if you share a small article, or the whole Encyclopedia Universalis)

You are welcome :)

You don't need it, but your familly do !

And key point is : what is the most likely place for them to start searching such information?

In my case, they will never thought about looking for an "emergency page". So laminayed cards mentionned by someone else seems to be a good option

I was thinking about such a system also, but it has some serious drawbacks:

  • I need to connect to it regularly. Auto login is of course not an option, that defeat the purpose. So, which service/stuff am I using that could be this switch? I see any.
  • time limit to send the message is also tricky. 2 weeks is too long imo, they may need some info about insurances sooner. And 2 weeks is already short, as you need to authenticate to the switch

So, as a farewell message why not, but I would not trust such system to deliver in a tilely manner information that they need.

I like that idea, totally non-nerds friendly.

Will look into that, thanks :)

Well, if you assume they are able to do copies of files, and in the end they are not, you will not go to heaven because you screwed up your familly.

Same as stop using the services, they might now even know they are using some @home services that are running in the background.

But I take the idea about having them making their own copy of files, and write down some instructions ablut what is where, and how do a backup they own.

I'm using a bunch of blocklists, and the only downside I've experienced is Teams being blocked.

Kind of problematic when you look for a job ><

But once you whitelist it, no problem