I did nothing and I’m all out of ideas!
I wish they used them all, especially XDG_CACHE_HOME
which can become pretty big pretty fast.
disable this system security feature temporarily,
This should be - if I’m not mistaken - possible using the pip env var I posted about earlier, like this:
PIP_BREAK_SYSTEM_PACKAGES=1 sudo apt install howdy
Or exporting it for the current shell, before running the installation
export PIP_BREAK_SYSTEM_PACKAGES=1
But I personally highly discourage it, because - AFAIK - if it even works it will mess up the deps in your system.
I’m no python expert but reading around it seems your only real solution is using a virtual environment, through pipx or venv as you already had found out, or using the
--break-system-packages
* Allow pip to modify an EXTERNALLY-MANAGED Python installation
(environment variable: `PIP_BREAK_SYSTEM_PACKAGES`)
pip flag which, as the name suggest, should be avoided.
EDIT: After rereading I got your problem better and I was trying to read the source for Howdy to see how to do it, so far no luck.
It’s an error with a dependency written in Rust, the workaround is to use an older toolchain (1.72), it is fixed in the newer code of tokenizers, but probably it is not updated in AUTOMATIC1111 yet: you should check their bug tracker
To have more info you can read this issue: Link
Considering you are not using the Flatpak anymore it is, indeed, strange. The only reasons I can think of are: your network manager is using the wrong network interface to route your traffic ( if you go on an ip checking site like for example ipinfo do you see yours or the VPN’s IP?) or that you have WebRTC enabled and the broadcaster is getting your real ip through that.
For the first case it can get pretty complicated, but it is probably an error during the installation of the VPN app or you set up multiple network managers and it gets confused on which one to configure. You should also enable the Advanced Kill Switch in the configuration.
For the second case you could try adding something like the Disable WebRTC add-on for firefox and check if it works. Remember to enable it for Private Windows too.
The last thing I can think of is that you allowed the broadcaster to get your real geolocation (in firefox it should be a small icon on the left of the address bar), or you are leaking some kind of information somewhere: there are a bunch of site that check for ip leak, but I don’t know if that goes too deep for you.
If you want to check anyway the first two results from DDG are browserleaks and ipleak. Mullvad offered one too but it is currently down.
EDIT: If you enable the Advanced Kill Switch, and the app is working correctly, internet will not work while you are not connected to a VPN server or until you disable the switch again, so pay attention to that.
Probably when you installed the second linux you overwrote the boot loader instead of adding a new UEFI entry point.
But I’ve never had a Mac, so take this with a pinch of salt, and honestly considering things can change based on what, in which order, and how you installed things… it could be something else.
Unfortunately, in general, people tend to just read, vote, and then forget about it without checking back: that’s why I always try to add some source or ways to verify what I post.
And - in this specific case - probably some people just like LTT, I assume.
Linus is an investor in the framework company: Source on the framework forums that links to the video on youtube
Why not directly link to the video? Because I don’t want to! :P
I feel there’s some kind of miscommunication going on here.
Probably I’m not understanding what you are putting forward, but to be clear: They are not doing this because they want to. They are doing it because they are forced to do it by the DMA.
It’s true that allegedly they were working on some kind of interoperability layer already. For years now. But no evidence of it being more than lip service to avoid being regulated has ever surfaced - as far as I know.
Which would have been in line with your “Do Nothing”.
as an unwilling Whatsapp user the ability to migrate without having to convince all my social circles to do anything but check a checkbox sounds like a huge step forward.
That’s the point. I feel it will not be a “simple checkbox”, and they will make it the most obnoxious process they can using the Best Dark Patterns the industry has to offer.
Already the general public is not interested in the alternatives or the concept of interoperability - wanting something that Just Works™ - putting in front even the smallest step (and some scary text!) will make the percentage of willing people become even lower.
And that’s not all. As it is portraited in the article by the Threema’s spokeperson it is pretty clear that Meta will just try to make the maintenance of the communication layer as cumbersome as they can - both technically and bureaucratically.
They are explicitly the ones keeping the reins of the standard, the features, the security model, the exchanged data and who, how and when will be approved.
So from one side if they make it hard and scary enough to tank the use rate, they will have the excuse of not being there enough people to give priority to fix it or add features, and from the other side if maintaining the interoperability will be difficult and time consuming enough, the people and businesses from the alternatives or wrappers will not have the incentive to do or keep doing it for the long haul. As we can already see in the article.
Is it better than nothing? Sure, probably. Will it be a slow cooking, easy to break, easy to get excluded from, just bare minimum to comply to the letter but not the spirit of the law? I feel that’s a pretty good bet to make.
Let’s be clear: I will be extremely happy if all the red flags and warning bells that I saw in the article will just end up being figments of my imagination. But yes, I’m very pessimistic - maybe even too much - when I see these kind of corporate speech and keywords.
“One of the core requirements here, and this is really important, is for users for this to be opt-in,” says Brouwer. “I can choose whether or not I want to participate in being open to exchanging messages with third parties. This is important, because it could be a big source of spam and scams.”
Let me translate this for you: "We will make users hop on the most cumbersome, frustrating and inefficient way we can think of to enable interoperability. And making it defaulted to off will mean people using other apps will need to find other channels to ask for it to be enabled on our users’ end, making it worthless.
And don’t forget: we will put a bunch of scary warnings, and only allow to go all in, with no middle ground or granularity!"
Great stuff, thank you. I can’t wait.
“We don’t believe interop chats and WhatsApp chats can evolve at the same pace,” he says, claiming it is “harder to evolve an open network” compared to a closed one.
Ah, so they are going for the Apple’s approach with iMessage and Android sms. Cool, cool.
I hope my corporate-to-common translator is broken, because this does just sound bad.
Any foundation model is trained on a subset of common crawl.
All the data in there is, arguably, copyrighted by one individual or another. There is no equivalent open - or closed - source dataset to it.
Each single post, page, blog, site, has a copyright holder. In the last year big companies have started to change their TOS to make that they are able to use, relicense and generally sell your data hosted in their services as their own for the intent of AI training, so potentially some small parts of common crawl will be licensable in bulk - or directly obtained from the source.
This does still leave out the majority of the data directly or indirectly used today, even if you were willing to pay, because it is unfeasable to search and contract every single rights holder.
On the other side of it there have been work to use less but more heavily curated data, which could potentially generate good small, domain specific, models. But still they will not be like the ones we currently have, and the open source community will not be able to have access to the same amount and quality of data.
It’s an interesting problem that I’m personally really interested to see where it leads.
Give technitium a go, my woes diminished drastically with that.
There’s an archived snapshot of the issue: https://web.archive.org/web/20220623132457/https://github.com/GrapheneOS/os-issue-tracker/issues/820
Are you talking about this: https://lemmyverse.net/communities ?
There’s this one too: https://browse.feddit.de/ but it is not as nice.
I’ve posted a top level comment with all the concepts I think could be useful to better understand the whole Fediverse and Lemmy thing: if ,after that, you have any more questions you can reply to it and I’ll try to help you out.
I’d link it directly but currently comments links can get messy.
I’ll try to simplify some concepts about the Fediverse and Lemmy using some more common IT knowledge.
I assume you are familiar with emails: gmail, protonmail, hotmail, aol, each of them runs a Server which will give you access, when registered, to a mailbox which will have a name of your choice, followed by an AT(@), and then a Domain specific to the vendor you have chosen.
Lemmy works in a similar way: When you choose an instance (for example lemmy.world, or lemmy.ml, or feddit.de, you can find a list here: https://lemmyverse.net ) you are choosing where your account will live. You’ll get a full ID composed by your name of choice followed by an @ and then the domain of your chosen instance.
In your case your full ID is favrion@lemmy.world . This is unique to you in the whole Fediverse.
Contrary to emails we have another abstraction: Communities. They are collections of posts and comments, moderated by someone and about a specific subject. These communities will reside on a specific server, like your account, and you can, for example, go to !technology@lemmy.ml or !mildlyinfuriating@lemmy.world . As you can see their format is similar to that of your account: they have both a community name, the name before the @, and a domain that specifies where the main copy of it physically resides.
You can find a full, searchable, list of communities here: https://lemmyverse.net/communities For some more complex reasons just disregards any of them that reside on beehaw.org (they have defederated with lemmy.world, but you don’t need to understand this concept yet).
When you start to look around the lemmy.world site, and you are logged in with your lemmy.world account, you’ll have the ability to follow three different types of feed: Subscribed, Local, All.
Local: This feed shows only communities which main copy actually resides on the instance that you are currently on.
All: All the posts from all the communities of all the instances will appear here.
Subscribed: All the posts from the communities that you have subscribed to will show here.
Until now the concepts were pretty straightforward and not so dissimilar from other services, but now starts the more complex subject: Federation.
For all this different instances (computers running the Lemmy server) to have the information it needs to spread and they need to duplicate it.
This will allow you to see the same exact content whichever instance your account is on: this means that if you have chosen to create an account on lemmy.world or lemmy.ml it, generally speaking, doesn’t matter. You will see and interact with the same content and people.
Your instance is just the gate towards the content, which you have to always pass through (so no, you shouldn’t make an account in each instance, you just need one, and you should choose an instance which rules and values are acceptable for you and, better yet, similar to yours).
Going back to the previous comparison with email services you can think of this as: Each time you take an action (writing a post, a comment, sending an upvote) you are really just sending an email to all the instances, so they get notified and update their copy of the content.
An email saying something along the lines of “favrion@lemmy.world has just downvoted the post number 69420 in the community 42 of the instance 123” will propagate until every single server has received it.
Defederation is the strength and the weakness of the whole fediverse: it helps to moderate the content but it also breaks the web connecting all the servers.
Each instance automatically connects itself with all the others present in the net, but an Admin can actively decide that some other instance - maybe because it is full of Bots, or Scammers, or contains communities clearly voted to illegal or immoral things, or just they don’t like it; the reasons are subjective - really rustled their jimmies and they don’t want to see it anymore. In that case the Admin could decide to Defederate from them: this means that each time a new email from that instance comes it just get dropped and ignored.
So, if Instance A defederates from instance B, each time B sends an update to the content produced by the communities or people from B it will just be ignored by A. All the users registered on A will just not see anything or anyone from B.
Basically an instance wide shadow-ban.
This was just a quick and rough explanation of the concepts, but I hope it was useful: if you have any question I’ll try to answer them at the best of my abilities. But keep in mind that they are not really high. And I’m kinda tipsy.
The main takeaways are this:
EDIT: Typos.
The pending thing is just a weird bug. For all intents and purposes you are subscribed and you will able to see it in your Subscriptions feed.
It’s probably a problem with the UEFI, the windows info got overwritten, and you can probably fix this with efibootmgr
It happened to me too, but unfortunately it was some years ago and I’m not at home to find the related notes that I took. I remember there was a windows utility to rewrite the boot loader. But probably in your case the boot partition is still okay, just the UEFI entry got overwritten and you just have to add it back manually.
Check the troubleshooting section of the wiki page to have a tip on the windows booting location