And you installed all the dependencies listed in the dependencies section and the following section (specifically winetricks and yad)?

Other than that, I never had any trouble installing it.

Arch Linux. First on i3, later on wayland with Sway, where I had lots of flickering, so I’d use XFCE (with x11) specifically for Fusion work (so log out and log in with xfce when i wanted to use fusion). and now Niri, which works well enough for flickering, but has issues with fusion 360’s modal windows not being in the right place, so i use a Labwc window inside Niri and force Fusion to run in that, mostly because i grew tired of switching to xfce. I would recommend xfce if you want less hassle. Haven’t tried with gnome or kde.

Do you remember what issues you had? Whenever i had trouble in the past (e.g. with logging in), i usually found a solution in the github issues (i guess both GH aud codeberg issues now that the project moved)

Oh you’re right, it’s moved to codeberg. I’ve updated my original post. Lots of projects moving off of github recently, because Microsoft. In my experience crinklyfly is very active in maintaining the repo, so hopefully this will continue on codeberg.

I’ve been using it through wine for two years now, using this repo.

It works surprisingly well, sometimes there’s some flickering, but not enough to prevent me from working. It gets a bit slow to react on big assemblies, though that might also be the case on windows. logging in is a pain, luckily that’s only every 1-2 months (you need to log in on the homepage, copy the login id and run a cli command with the id, within the 30 seconds before the id expires. Usually takes me 2-3 tries because i forget it after 2 months). it not seeing linux drives and having to copy files from/to wine’s drive_c is a bit annoying.

but overall it’s good enough, haven’t booted the windows partition in those two years and I’m willing to deal with this to be windows free. But if i had to use it professionally as a daily driver, that would probably be different.

I did have to reinstall it twice in the two year period, though.

You can find a cleaned up version here

Someone over on lobste.rs has deobfuscated it, code can be found here

Venta LW45 humidifier. easy to clean, uses like 8W/hour (compared to ~40 for ultrasonic or 300 for electric heating ones), quiet, goes through a 9l tank per day easily. And has almost no part that could break i.e. i could replace whatever could break easily.

but the price is insane for what amounts to a bucket with a fan

I wanted to punch someone when i realized my Bosch drill and Bosch electric saw use different batteries. They’re identical in size, but the plug part on one is a mirror image of the other and so not interchangeable

Meshcore has a default public channel, and usually several optional other public ones as well, depending on where you’re located. Usually there’s also some online community/forum for each country/region where people organise themselves.

Yes, i hate this in these kinds of discussions. It so often devolves into how you’ll be safe from surveillance by world governments (spoiler: you won’t be, if they really care).

And here I am, just not wanting to hand data over to giant corporations that have been proven to use it for no good.

Heck, even if there was no good actor/solution, not giving all your data to the same bad actor is already a step up.

heck if anything, the Fediverse, as it is right now, is more susceptible to this. You can spin up spam instances on new domains, with spam users, and have them federate to existing instances, faster than volunteer run instances can ban/defederate.

So you end up with not federating by default, but having some trusted web of instances that federate and maybe an approval process for new instances to federate with? But that’ll still lead to centralization with “trusted” instances and new instances having a hard time to join the club (there’s also the scaling problem of the fediverse, but that’s besides the point). So you end up with a few very big instances and the owners of those instances having all the power. Or maybe small isolated islands of mutually trusting instances? Still better than tech oligopoly, but also a far cry from the original dream.

I feel Authentik is at the sweet spot between complexity/features (keycloak) and ease of setup (authelia)

Afaik to poison AI data.

Of course if it’s only them doing it, it will be too little data to affect AI training. And if enough people do the same to affect the training, it’d just be the way we talk now and AI wouldn’t be affected either. So it’s pretty pointless, but with bad externalities (being annoying), much like AI…

A big issue is that this works for bots that announce themselves as such, but there’s lots that pretend to be regular users, with fake user agents and ips selected from a random pool with each ip only sending like 1-3 request/day, but overall many thousands of requests. In my experience a lot of them are from huawei and tencent cloud/ASN

I don’t actually know how nostr deals with messages if you’re offline, if at all, not that familiar with the protocol. But your idea sounds workable.

I tend to come at it from the other side, I like the federated model, but think the “supernodes” could behave more like dedicated relays. Like, a lemmy server right now does a lot of things, like serve a frontend, do expensive database queries to show a sorted feed, etc. and a lot of that does not scale very well. So having different kinds of nodes with more specialization, while still following a federated model makes sense to me. Right now if one of my users subscribes to some community, that community’s instance will start spamming my instance with updates nonstop, even though that user might not be active or might not even read that community anymore. It would be nicer if there was some kind of beefy instance I could request this data from if necessary, without getting each and every update even though 90% of it might never be viewed. But keeping individual instances that could have their own community and themes, or just be hosted for you and your friends to reduce the burden on non-techies having to self-host something.

Or put another way, instead of making the relays more instance-y, embrace the super instances and make them more relay-y, but tailor made for that job and still hostable by anyone, if they want to spend on the hardware. But I’m still not clear on where you’d draw the line/how exactly you’d split the responsibility. For lemmy, instead of sending 100’s of requests in parallel for each thing that happens, a super-instance could just consolidate all the events and send them as single big requests/batches to sub-instances and maybe that’s a good place to draw the line?

it’s iocaine not Locaine, tripped me up at first as well.

this article and the accompanying discussion from lobsters is very relevant. Though the article itself is a bit one sided in favor of nostr, it doesn’t do a great job arguing why a relay really is better

What you said is like “i’m going to delete linux and install ubuntu”, but then there’s not really a name for the android that comes with your phone. “stock android” probably is the closest term you get to distinguish between the OS family and the thing actually installed, but all the companies customize their android, so it’s not like there’s just one “stock android”.

i mean, I’m sure samsung has some term for their android, but i doubt anyone use this outside of samsung.

Pinta is my goto replacement for paint.net on linux. It also loads really fast and has most of the basic editing needs covered.

You mean for the referer part? Of course you don’t want it for all urls and there’s some legitimate cases. I have that on specific urls where it’s highly unlikely, not every url. E.g. a direct link to a single comment in lemmy, and whitelisting logged-in users. Plus a limit, like >3 times an hour before a ban. It’s already pretty unusual to bookmark a link to a single comment

It’s a pretty consistent bot pattern, they will go to some subsubpage with no referer with no prior traffic from that ip, and then no other traffic from that ip after that for a bit (since they cycle though ip’s on each request) but you will get a ton of these requests across all ips they use. It was one of the most common patterns i saw when i followed the logs for a while.

of course having some honeypot url in a hidden link or something gives more reliable results, if you can add such a link, but if you’re hosting some software that you can’t easily add that to, suspicious patterns like the one above can work really well in my experience. Just don’t enforce it right away, have it with the ‘dummy’ action in f2b for a while and double check.

And I mostly intended that as an example of seeing suspicious traffic in the logs and tailoring a rule to it. Doesn’t take very long and can be very effective.