• 2 Posts
  • 55 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle






  • It should still work!

    I only go back and make changes to LED if something breaks with a major Lemmy update, but Lemmy hasn’t had a major update since January. Lemmy v0.19.4 isn’t released yet, but when it is, I’ll make sure the deployment is up to date.

    Note that it does not have any advanced features that a major instance might want, such as storing images on S3, exporting data, or image moderation. If you intend for your instance to grow for 100+ users, this isn’t for you. This is only intended for beginners who are overwhelmed by the other Lemmy hosting options, and want an easy way to host a small single-user or small-user instance.




  • I still don’t like how flippant they’ve been in every public communication. I read the ToS. It’s short for a ToS, everyone should read it. They claim it was taken “out of context,” but there wasn’t much context to take it out of. The ToS didn’t make this distinction they’re claiming, there was no separation of Vultr forum data from cloud service data. It was just a bad, poorly written ToS, plain and simple.

    They haven’t taken an ounce of responsibility for that, and have instead placed the blame on “a Reddit post” (when this was being discussed in way more detail on other tech forums, Vultr even chimed in on LowEndTalk).

    As for this:

    Section 12.1(a) of our ToS, which was added in 2021, ends with “for purposes of providing the Services to you.” This is intended to make it clear that any rights referenced are solely for the purposes of providing the Services to you.

    This means nothing. A simple “we are enhancing your user experience by mining your data and giving you a better quality service” would have covered them on this.

    We only got an explanation behind the ToS ransom dialog after their CMO whined in a CRN article. That information should have been right in the dialog on the website.

    In both places, they’ve actively done vague things to cause confusion, and are offended when people interpret it incorrectly.



  • Makes sense. The article calls it “unwarranted gatekeeping,” but they wouldn’t say that if they knew how Android internals work.

    Looking at the video demo for Circle to Search, it’s very likely they built this on top of ActionsServices, an Android component that enables extra interactions on top of the Recents switcher. This is already what’s being used to do things like OCR in the Recents switcher.

    Other non-Google ROMs use ActionsServices too, but their implementations vary, and they can’t just “tack on” something as complicated as this onto any vender implementation of ActionServices and expect it to work. They might not even have a vendor rollout plan for this thing yet, for all we know it was rushed out the door.

    Google has had a tight partnership with Samsung since the Pixel 6 came out, which is why it doesn’t surprise me that Samsung will be getting this feature first. Google can essentially boss Samsung around for little system things like this.

    The “for a long time” comment was probably due to Android 15 already being mostly final at this point. I wouldn’t be surprised if there were core changes to Android to allow more pluggable customizations to the Recents switcher in Android 16. That might enable Google to offer this feature to other vendors more cleanly (assuming the feature survives that long, which is doubtful).



  • Hi :)

    If you’re already running an instance, you’re not going to have a good time of this on the same server unfortunately. The webserver config I ship assumes a single instance, and all of the handling assumes only one domain. You would have to basically modify my entire script to support something like this.

    You can take a look at my advanced configuration page to figure out what files you can edit, but this would be a very manual process for what you want to do.

    Apologies, but you would be better off deploying a new server.




  • The person you replied to is being downvoted, and yes, expecting support from Google is a meme, and Google deserves 100% of the negativity they’re receiving in this regard.

    But, in their defense, they have always kept their word on keeping Pixels updated, and in some cases, have added on an additional year of support when not originally planned, including an extra full Android update for older devices.

    So while they eventually kill every new software product they make, they’ve always kept their word on Pixel updates. I think the Pixel team has a lot more resources than the rest of Google, so I’m inclined to believe them for now, but I’ll be one of the first people grabbing a pitchfork if they don’t keep their word.