The tl;dr is that the play version of termux has been lagging behind the master github branch because of Google’s fuck fuck games with Android permissions. Now it’s been updated, but effectively neutered.

Basically, PlayStore termux-app v0.120 release is functionally equivalent to v0.108

Cobalt.tools worked flawlessly!

EDIT: Ope, thought you were asking lol. Cobalt.tools rocks!

I’m just curious as to how you think these are insurmountable problems while every instance in existence today is already managing to navigate these issues.

The only thing the author is suggesting is to pool the resources that are going to waste copying media posts around the fediverse into a new backend (that means it’s not directly user accessible and presumably subject to the same restrictions as posts right now) so that the cost of media hosting is more distributed between all the fediverse instances instead of having the big ones hogging all the bandwidth of the small ones with memes because some users decided to subscribe to a community on say Lemmy.world.

Did you even read the article? It’s not like all the users just get unrestricted access to storage to treat like a google drive, this is a backend thing. This guy is trying to find a solution to all the wasted bandwidth and storage space from sending copies to all the other instances they’re federated with, which is a legimate issue that the instance admins are already dealing with on a daily basis. This will let them pool resources to help lower costs for smaller instances.

As to the CSAM thing I can only imagine it would be easier for one instance to purge fifty images/restore from a backup and everyone else just have to redo their thumbnails as opposed to all the instances having to purge and restore but that’s just me.

@dansup@mastodon.social is working on loops, a federated tiktok. According to THIS POST it looks he’s going for optimizing the uploaded video format over microtransactions for reducing overhead.

They also went blind

Yeah we’re about due for the bell riots, aren’t we?

Well of course not, ever since they got that deal with Uncle Sam they knew they could do anything up to Steve Ballmer kicking a secret service agent in the nuts and stealing the Football. Maybe even including that, won’t know until it happens lol.

“Why aren’t we making more money?!?” Cries Phil Spencer while wringing the neck of yet another golden goose.

This is fantastic!

… Should someone tell him?

Is this the ewok that you could cheat into Galactic Battlegrounds? It looks familiar…

I’m in the process of doing this with my former employer (NLRB complaint). It’s not as much trying to get your job back as getting what you’re owed, be it severance or your pound of flesh lol.

A lot of contracts specify that you have to go through arbitration to resolve disputes with the company as opposed to the courts, which is both good and bad. Bad because it takes a while and they’re usually all buddy buddy with the people who pay them, but good because arbitration is pretty expensive and making them do all this when they’d rather be done with you brings me joy.

Also this gives companies the opportunity to use more rope to hang themselves with if they try to do funny stuff with their arbitrator, the NLRB can overrule arbitration decisions if they’re “repugnant”.

Oof, that’s what killed my V1 setup lol

They couldn’t effectively serve ads through it lol

I did just check to see if you can pass along wildcards in an automation, which you can! I used this automation:

alias: sentence test
description:
trigger:
  - platform: conversation
    command:
      - When is [my] {date}
condition: []
action:
  - set_conversation_response: curses, that damnable {{ trigger.slots.game }}
    enabled: false
  - choose:
      - conditions:
          - condition: template
            value_template: '{{ ''birthday'' in trigger.slots.date }}'
        sequence:
          - set_conversation_response: >-
              curses, that damnable {{ trigger.slots.date }}! It completely
              slipped my mind
      - conditions:
          - condition: template
            value_template: '{{ ''christmas'' in trigger.slots.date }}'
        sequence:
          - set_conversation_response: sir you know when {{ trigger.slots.date }} is!

This should give you a framework to build off of. It looks like when you don’t define a list of slots in an intent it just passes the wildcard along in a slot.

I can think of a couple ways you could have it be one automation, the first is you’d have multiple triggers with different ids and use the choose action to select the response based on the trigger id.

The other way that I’m a bit less sure about is passing the name of the input_date helper through to the response with a wildcard. You’d probably have to set the {{ trigger.slot.event }} as a variable and match that to an alias or an entity_id.

So I found this which might help. I tried defining my own intent scripts too, but it was too much of a PITA, I ended up using automations instead.

Not out yet unfortunately.

EDIT: I lied, link is here. There’s no releases as of yet.

Or get a geofence warrant