Redjard

joined 2 years ago
[–] Redjard@lemmy.dbzer0.com 2 points 6 hours ago

Yes, it's a fancy way to turn a link containing encoded text into that text.

[–] Redjard@lemmy.dbzer0.com 5 points 15 hours ago (1 children)

At the very least the system should initiate an emergency break when it disengages like that and there is no conflicting human input.

[–] Redjard@lemmy.dbzer0.com 3 points 3 days ago (1 children)

The modlog on your instance has a few entries with "reason: automod".
These all aren't present on the actual sub.
Another example here is

which still exists on lemmy.world.

This post has less than 30% vote ratio and more than 50 votes. There might be a cutoff under which shit.just.works simply removes content.
Which if true I gotta say kinda sucks. Maybe a remnant from the cp catastrophe?

You better get used to visiting the home instance of posts whenever you see a removed comment you wanna read. Most apps should have a "source link" option, usually with the fediverse symbol, which should open the post on the "ownership" instance, so the one authoritative over what the comment looks like. My app (summit) even offers that per commend conveniently.

[–] Redjard@lemmy.dbzer0.com 2 points 3 days ago (3 children)

Compare these:
https://sh.itjust.works/post/34698028/17414247
https://lemmy.world/comment/15793837

The user is on lemmy.world, where the comment is gathered by all other instances. It is visible for me on dbzer because that pulls from lemmy.world where it still exists.
I assume your instance admins deleted it locally for your instance only. Who knows why. I suggest you move to a different place that doesn't randomly moderate external sublemmys for local users only.

[–] Redjard@lemmy.dbzer0.com 2 points 4 days ago (5 children)

Was it? I still see it.
Maybe your reader auto hides it due to the low rating?

[–] Redjard@lemmy.dbzer0.com 2 points 4 days ago

I don't understand your question.

[–] Redjard@lemmy.dbzer0.com 2 points 6 days ago* (last edited 6 days ago) (1 children)

They’re both copyleft so no chance of a rug pull.

That's not accurate. It also takes an absence of a cla (Contributor License Agreement) transfering ownership of patches and a diverse set of major contributors to develop that protection.
GPL protects against outside entities taking over a project via a fork, owners are always free to change the license of what they made.

I didn't see a cla on either libreoffice online nor onlyoffice, but you would have to contribute some actual changes to see you don't need to agree to anything and they will accept your contributions without rewriting them later.

In comparison for example audacity makes you transfer rights over code contributions to them. That means they could make audacity closed source at any time and any version from that point would be proprietary. Would they not force contributors to sign that cla, and instead go with a copyleft contribution license, then with going closed source they would violate the licenses under which they use all these contributions.

Basically distributed ownership prevents rug pulls, since ownership beats license restrictions. So you have to check that a project has spread out ownership (independend major contributions) connected by copyleft licenses (standard unless overridden by a (non copyleft) cla)

[–] Redjard@lemmy.dbzer0.com 7 points 6 days ago (1 children)
[–] Redjard@lemmy.dbzer0.com 32 points 6 days ago (1 children)

Fossil gas was a minor energy source for germany and the eu. It was costly to replace 2 years ago but at this point the cost has been paid and the energy is sourced from other fuels.
The german car industry was bound to fall ever since they refused to research electric cars decades ago. Even before then they had been outsourcing but now they simply don't own the profitable part of electric cars - the battery and power-train.
With or without the war in ukraine they would be disappearing.
The overall german economy is fine, there is increasingly unequal distribution of wealth like many western nations in recent decades, but the economy is ok.

Ps: I don't recall the numbers for germany, but pre 2022 the EU generated less than 20% of their energy with fossil gas, and less than 14% of their electricity. Germany had a higher ratio, but definitely less than a third.

[–] Redjard@lemmy.dbzer0.com 2 points 3 weeks ago (1 children)

Seems centered on books not papers

[–] Redjard@lemmy.dbzer0.com 29 points 3 weeks ago (1 children)

And of

Very neat

 

cross-posted from: https://jlai.lu/post/14117725

47
submitted 5 months ago* (last edited 5 months ago) by Redjard@lemmy.dbzer0.com to c/factorio@lemmy.world
 

With the update there was an overhaul of what combinators can do.
I had the problem that my oil cracking would flicker, turning on for a split second then back off again, hovering right around the set threshold. (Probably worsened by me not switching a pump anymore like what used to be the norm.)

The old method would have been an SR latch, which enables at a higher set point and disables again at a lower reset point. This used to take 3 combinators.

~~I figured it should be possible to do better now, but could not come up with a way to cram an sr latch into a single combinator, since it can only be either on or off at one time. I think it takes two combinators to build an sr latch now.~~
A single-combinator SR latch is in the comments.

Instead I came up with another way to "debounce" my cracking.

Here shown is the combinator sending the signal to enable cracking (the recipe icon of light oil cracking) while the actual activation signal, light oil above 20k, is off.

The signal was on for a moment, then after the cracking started up the oil level immediately dropped below 20k again. But now the second condition, T between 0 and 10s, is active. While the combinator is active, it is sending out 1 plus the old count to T, counting it up once per frame. It remains active while the condition is active or while T is counting up but has not yet reached 10s (at 60 ticks per second). This ensures that every time the cracking runs, it runs for at least 10 seconds.
After these 10+ seconds, the level should take a while before rising above the threshold again.

For me, this successfully made the row of chem plants turn on in one smooth go.

 

3x the previous all time high just shy of 35k in August 2020 when 1.0 released - on a Friday during the pandemic.

1
Plan transition timing (lemmy.dbzer0.com)
submitted 1 year ago* (last edited 11 months ago) by Redjard@lemmy.dbzer0.com to c/nebula@lemmy.world
 

2 month update: Just got this mail

Your Nebula Subscription
We're writing to let you know about a change to your Nebula subscription. Curiosity Stream deactivated your bundle access to Nebula on February 22, 2024. Because you purchased your direct Nebula subscription while still having access to Nebula through the bundle, we're adjusting your subscription's renewal date to be one year after your bundle subscription was deactivated. Your updated subscription details are as follows:

Next Renewal Date: February 22, 2025
Subscription: Yearly
Amount: $30 USD

So that would also indicate double charging.

Answer:
The charge is immediate, but the 12-month plan starts when the bundle access ends.

Original question:
Got the info that my curiositystream bundle, started mid april, wouldn't renew. I canceled the bundle on curiositystreams side and used the process the unbundle page guides you through to change to a regular subscription. Which worked fine. But the subscription price got charged immediately, and I now have two subscriptions listed in my account:

The confirmation reads

Thank you for purchasing a subscription to Nebula.

Subscription: Yearly
Purchase Date: February 21, 2024
Amount: $30 USD

Am I essentially getting double charged for 2 months here? If so, what would have been the right procedure?

 

I updated my firefox from 119.0.1 to 121.0 two days ago, and have noticed a for my usage quite significant change:
When I have a page, say a search engine query or a gallery of links on a page, and I open one then go back, previously I got the cached version. Within reason of the cache size I could go back a few pages even days later and critically see them as they where, just like I would expect for a tab I have open.

I use this behavior to work through essentially todo lists, so now that the lists get reloaded every time I visit them, this combines with server side caching to make the list jump around quite annoyingly.
My expected behavior would be the cached back history being served when available, except when I manually hit F5.

Was this change intentional? Is there any way to get the old behavior back?

Edit:
It seems to be a bug and only happen on some profiles, potentially dependent on some metric related to heavy use, like number of open tabs and windows.
Edit:
It seems to be related to uBlock Origin.
Edit:
It is definitely an issue within ubo, I will add a link to the issue there when I create it.
Edit:
It seems to be caused by the "AdGuard Tracking Protection" filter list within ubo.
Edit: issues:
ubo filters: https://github.com/uBlockOrigin/uAssets/issues/21841
AdguardFilters: https://github.com/AdguardTeam/AdguardFilters/issues/170172
Edit:
It was fixed a few minutes ago, the changes should percolate through to ubo soon™. Thx Yuki2718.

view more: next ›