ambitiousslab

You can trust the software in your distro's repositories (if you run a distro with well-maintained repositories). This is because, generally only well-known software gets packaged, the packager should be familiar with both the project and the code, and everything is rebuilt on the distro's own infrastructure, to ensure that a given binary actually corresponds to the source.

It might still be possible for things to slip through, but it's certainly much safer than random programs from online.

I independently thought of the same idea. While I'm daydreaming, I had some extra features that would be useful to me in a dream world:

• It would be good to be able to apply this to posts (that are not mine) as well, or even to a link (i.e. all comments that would show up under the crosspost aggregation feature)
• One problem I have with GitHub is that the subscription list perpetually grows and is never pruned.
  • It would be nice if I could make such subscriptions, for instance, automatically expire n days after the last interaction
  • Or, if there is a list of subscriptions somewhere, if I could manually "prune all whose last interaction is more than n days"
• I'm not sure what the best UI would be, whether everything should go in notifications, or whether there should be a dedicated view for these subscriptions
  • And, should that view show the whole thread underneath the top-level post you subscribed to?
  • Or just the "new" comments?
  • My feeling is the former, but not sure.

Now, I'm not asking companies to open-source their entire codebase. That's unrealistic when an app is tied to a larger platform. What I am asking for: publish a basic GitHub repo with the hardware specs and connection protocols. Let the community build their own apps on top of it.

I agree with this. I think the most important thing is not necessarily the original company releasing their proprietary code (although that would be nice), but it being easy (and legal!) for hackers to reverse engineer and/or build on top of the platform.

The irony is that, since most such products will have some GPL'd code in there somewhere, most products already basically have such a requirement, thanks to the section requiring complete corresponding source including installation instructions. Hopefully, the Vizio case will establish the precedent that users, as well as copyright holders, can take action against such companies.

This might be a silly question, but in what ways did it get worse? Is it the size of the keyboard changing, the predictions not being as good anymore or something else?

With my knowledge of tech companies, I'm not exactly surprised, but I'm not an iPhone user and struggling to understand how a keyboard of all things could get worse.

For me, it would be for her to actually respect my boundaries, and to show an active interest in who I actually am instead of what role I can fulfill for her.

Wait is this how you get up to date when your system is past long term support?

Pretty much! You just modify the apt sources, and upgrade incrementing by each stable release until you reach current stable. Each upgrade guide has a section that points you to the guide for the previous version if your version doesn't match.

Would not recommend doing backups drunk.

:D in my experience, there's a certain amount of drink-inspired overconfidence that can be helpful, but it's very easy to go over. I need more testing to find the exact line - it might also wrap around again if you drink more. More investigation needed :)

I have mixed feelings about this. If this leads to more investment in local services, then that's good.

I don't like that I haven't seen a clear public debate. In some countries we've seen "there are too many AirBnBs" -> "we need to disincentivise tourism" -> "we need a tourist tax". But that doesn't seem to have happened here (or I've missed it).

Have we decided as a city whether tourism is something we want to incentivise or disincentivise? Of course there are many pros and cons, but it feels to me that we haven't had that debate, and really Westminster is just scrambling to find a new group of "non-working-people" that they can let cities slap a tax on, to avoid funding local government properly.

If the tax was set up as a way to directly combat the effects of tourism, like building more housing, I would probably be more keen.

There were some breakthroughs in postmarketOS with the BlackBerry KEY2 recently. I really hope a phone with the Blackberry Classic form factor gets good mobile linux support in the next few years (bonus points if it's a linux-first device!) A physical keyboard (in that form factor) is one of the few things that could convince me to ditch the Librem 5.

I grew up on the tail end of Blackberry's dominance. Most of the people in my school had a Blackberry, I've always envied those keyboards, and I feel really nostalgic about them.

There's something special about that form factor that appeals to me more than the N900 or clamshell designs. I think it's that they're happy to compromise the screen for a great keyboard, rather than the other way round.

I'm happy this has happened. I'm still pretty wary, though. Can there be a cross party debate and agreement on what the limits should be? I worry the "mandatory" part will just get pushed through later on, like the encryption backdoor clause of the OSA.

This is me, but with OpenTTD :D

By dumbing down the suite, are you talking about things like flatpak / atomic distros?

If so, I am also not a fan of those things - give me Debian stable and the software in the repos and I'm happy - but I also don't think I will be harmed by others coming in and trying different approaches. From what I can tell, with each paradigm shift, the old approach doesn't go away, but stays powered by the volunteers who care about it.

I will give my guest a three course meal!

• Starter: Mackerel sandwich
• Main: Half a frozen pizza
• Desert: Lidl's fake Ben and Jerry fish food ice cream