Lemdro.id

2,298 readers
16 users here now

Our Mission 🚀

Lemdro.id strives to be a fully open source instance with incredible transparency. Visit our GitHub for the nuts and bolts that make this instance soar and our Matrix Space to chat with our team and access the read-only backroom admin chat.

Community Guidelines

We believe in maintaining a respectful and inclusive environment for all members. We encourage open discussion, but we do not tolerate spam, harassment, or disrespectful behaviour. Let's keep it civil!

Get Involved

Are you an experienced moderator, interested in bringing your subreddit to the Fediverse, or a Lemmy app developer looking for a home community? We'd be happy to host you! Get in touch!

Quick Links

Lemdro.id Interfaces 🪟

Our Communities 🌐

Lemmy App List 📱

Chat and More 💬

Instance Updates

!lemdroid@lemdro.id

founded 2 years ago
ADMINS

!lemdroid@lemdro.id is now open for general instance discussion and feedback

26
 
 

Revolt became Stoat

Cool new name, however not as easy to use in other languages.

Voice chat is stil not officialy implemented.

Self-hosting there. Apparently nothing to do for you if you had already hosted before the name change.

The Android app has unfortunately disappeared (not been updated) on F-droid.

27
28
9
Photon v2.1.1 (self.photon)
submitted 6 days ago* (last edited 6 days ago) by Xylight to c/photon
 
 

What's Changed

  • design: make media embeds not look like garbage
  • design: make error containers not look awful
  • design: make big community cards not look awful (and make them fully clickable)
  • fix: photon accidentally took inspiration from every article site ever and would autoplay videos from posts when you navigated. this was fixed
  • fix: a poor, alone button was in the command palette. i joined it with the other ones so that you can actually navigate with arrow keys and it looks better
    • it also got a friend, an option to search communities.
  • fix: i made a workaround for a svelte bug (i think). somehow, it would render an {#if} branch even if the condition was false, specifically if you had a dynamic component anywhere. this caused post feeds to have stale data when switching accounts.
  • fix: automatically strip leading https:// from the login prompt, for people who interpret "server domain" as the full fwicking url
  • fix: CommentItem had a shadow when it shouldn't've (that's a word?)
  • fix: when you went to edit your post, it would crash. i fixed

Full Changelog: https://github.com/Xyphyn/photon/compare/v2.1.0...v2.1.1

29
9
submitted 6 days ago* (last edited 6 days ago) by Maroon@lemmy.world to c/openwrt
 
 

I currently have a Phyhome P20 ONT setup. When I checked the list of supported devices for OpenWRT, I couldn't find it there.

Are there ONT style devices that are OpenWRT compatible?

30
 
 

Project 'Nulide/findmydevice' was moved to 'fmd-foss/fmd-android'. Please update any links and bookmarks that may still have the old path.

Find My Device has moved (since V0.10, V0.12 as of writing) and if you are hosting the server yourself, you might have missed that and might be locked out of the website interface.

If you have autoupdates on FDroid for your client, maybe you did not see the info.

31
 
 

Despite growing up and living in a so-called "third world country" I kinda became a stereo child and a Walkman teen so I really like Sony radios, even having sometimes the chance to own one or two of them. One of these is a XDR-V1BTD which might be "old" now (your mileage may vary) but I really like it and want to share my thoughts on it for posterity sake since I haven't find much about this on the internet.

First of all, this one does not have DAB radio because, again, third world country. The only thing remotely similar to digital radio here is a few no-image channels in the DVB-T2 spectrum acting as "radio" so to listen to them you need to have a TV that can tune DVB-T2 (Colombia being the only weirdo that set its TV to use DVB-T2; the other countries in South America use the japanese ISDB-T standard; as of late, Sony won't ship Bravia TVs with internal DVB-T2 tuners here, so if you want to get a Sony TV to watch TV and listen to "digital" radio... import it from Europe or f you). So we are stuck with "old" radio - heard that the cost to migrate to something like DAB would be astronomical.

So with this background 90% of the time I use this radio is to listen to the local radio (a couple rock stations, the uni station, and some news and old music from AM sometimes). I've brought it up sometimes to camping or trekking too. Have used it as a bluetooth speaker like a couple of times and never with the audio output function. Have never used the NFC thing but I see why people would appreciate that it's there.

The thing has been with me for some time, around 2-3 years. Got it second hand and it was fairly expensive; several buttons were working at random, including the power button, so even turning it on or off was kind of a hit and miss thing. I guess the previous owner dropped it or something like that. Had it serviced and they managed to make everything work.

Things I like

The thing is absolutely great. I love its boxy form factor and that its chassis is made out of "wood" (MDF?) which gives it a unique character. The sound quality is top notch (at least for me, no audiophile whatsoever) and it has some kind of "surround but not 3D surround" quality, which fulls the room with its sound, even at a low volume, and you can't tell easily where the sound it's coming from.

I love that the screen is a backlight full dot-matrix (the light is bright enough to light my room when it's completely dark, and ith has three levels of brightness which is really great) and the wake up/alarm functions are a great thing to have. It's great that the light screen button has a bit of raised surface (unlike the other buttons) so it's easy to find it in the dark.

The preset buttons are a nice addition to it. The preset button #3 has a little raised button (sort of like the 'f' and the 'j' on desktop keyboards) so you can find it with your touch and locate the others with other fingers of your hand. The power button has some ("radial") texture on it so it also is easily identifiable with your touch. Same thing with the big "change station" dial.

Battery life is also great too. I have never ran into the situation where it goes completely blank. I wish something like this had existed when I was a kid, in the 90s, when if you had a "portable" radio the only option was A batteries that ran out fairly quickly - and even more if you listened to FM radio.

Overall I find the thing of great quality, sturdy and elegant.

Things I don't like

First and foremost, the 'dial' wheel - Not that I don't like it by itself, but that its function is to change stations. With a set of buttons for preset stations, I find it kinda odd that it seems the main purpose of the radio is to change stations - it would make more sense to me if that wheel were for turning volume up or down. Sometimes when I'm trying to press the volume buttons I move that dial accidentally with other part of my hand, thus changing the station in the process, which is a bit annoying.

Also, this may be completely just me, but I don't like that the 'idle' screen uses a big font for the clock numbers, and when it's turned on the radio uses another font, with small numbers, almost unreadable from more than 50 cm away. Which brings me to the

Things I wish

I'd like if those two fonts were one and the same size, and a different font of any of these two - I love the numbers font that came up with the Wahoo Element 2 series, they're tall and stylish and I imagine they would look amazing in that dot matrix screen. I wish there were a way to change that or, if it exists, I wouldn't know how to make it happen (I guess some low-level chip programming has to be involved).

Sadly, as mentioned at the beginning, DAB radio is not a thing here and probably never will, so it's not possible to auto-adjust the clock. It would be a nice thing to have. And it would be great if it was rechargeable via USB-C - the wall adaptor throws 5.8V to it so also am not sure if it's doable.

As mentioned before, I wish the big wheel 'button' were for controling the volume. Or at least that it had another dial like that to change the volume. Volume buttons are rather small in comparison (long, but thin) so sometimes it's hard to change the volume. It'd be great if it had a 'mute' button.

Also another "maybe it's just me" but I wish it had USB/SD/Micro SD slots where you could plug your card or USB thumb with MP3 (or OGG, FLAC, what have you) and play them on the thing and control the playback with both the buttons and the dial on the device and via bluetooth. It'd be amazing but also am not sure if there is a way to "hack" it to add to it that ability. I wish Sony launched a new revision of these things with such feature but alas regarding to radios, Walkmans and the like they seem to like to launch unique batches of devices.

32
33
34
35
36
37
 
 

This looks promising.

  • only 2mb
  • can load icon packs
  • customizable text size & color
  • customizable grid sizes
  • widgets if you care for them (i don't use any)

I use lawnchair because of it's extreme customizability.

Most Android launchers are just forks of AOSP’s Launcher3. I wanted to try something different—building from scratch while welcoming new developers and applying solid coding principles and best practices to keep the project alive for the long run. Open-source Launcher3 forks often end up abandoned because of their complexity, making it tough for newcomers to contribute. And, not gonna lie… a lot of them are still written in Java and rely on legacy APIs.

Meanwhile, many closed-source launchers are starting to get greedy—locking features behind paywalls and sneaking in trackers. My goal is to give everyone the joy of using powerful features without compromising privacy.

38
39
 
 

cross-posted from: https://lemdro.id/post/30431015

40
41
42
 
 

cross-posted from: https://lemmy.world/post/37439450

  S.B. No. 2420

AN ACT relating to the regulation of platforms for the sale and distribution of software applications for mobile devices. BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF TEXAS: SECTION 1. Subtitle C, Title 5, Business & Commerce Code, is amended by adding Chapter 121 to read as follows: CHAPTER 121. SOFTWARE APPLICATIONS SUBCHAPTER A. GENERAL PROVISIONS Sec. 121.001. SHORT TITLE. This chapter may be cited as the App Store Accountability Act. Sec. 121.002. DEFINITIONS. In this chapter: (1) "Age category" means information collected by the owner of an app store to designate a user based on the age categories described by Section 121.021(b). (2) "App store" means a publicly available Internet website, software application, or other electronic service that distributes software applications from the owner or developer of a software application to the user of a mobile device. (3) "Minor" means a child who is younger than 18 years of age who has not had the disabilities of minority removed for general purposes. (4) "Mobile device" means a portable, wireless electronic device, including a tablet or smartphone, capable of transmitting, receiving, processing, and storing information wirelessly that runs an operating system designed to manage hardware resources and perform common services for software applications on handheld electronic devices. (5) "Personal data" means any information, including sensitive data, that is linked or reasonably linkable to an identified or identifiable individual. The term includes pseudonymous data when the data is used by a person who processes or determines the purpose and means of processing the data in conjunction with additional information that reasonably links the data to an identified or identifiable individual. The term does not include deidentified data or publicly available information. SUBCHAPTER B. DUTIES OF APP STORES Sec. 121.021. DUTY TO VERIFY AGE OF USER; AGE CATEGORIES. (a) When an individual in this state creates an account with an app store, the owner of the app store shall use a commercially reasonable method of verification to verify the individual's age category under Subsection (b). (b) The owner of an app store shall use the following age categories for assigning a designation: (1) an individual who is younger than 13 years of age is considered a "child"; (2) an individual who is at least 13 years of age but younger than 16 years of age is considered a "younger teenager"; (3) an individual who is at least 16 years of age but younger than 18 years of age is considered an "older teenager"; and (4) an individual who is at least 18 years of age is considered an "adult." Sec. 121.022. PARENTAL CONSENT REQUIRED. (a) If the owner of the app store determines under Section 121.021 that an individual is a minor who belongs to an age category that is not "adult," the owner shall require that the minor's account be affiliated with a parent account belonging to the minor's parent or guardian. (b) For an account to be affiliated with a minor's account as a parent account, the owner of an app store must use a commercially reasonable method to verify that the account belongs to an individual who: (1) the owner of the app store has verified belongs to the age category of "adult" under Section 121.021; and (2) has legal authority to make a decision on behalf of the minor with whose account the individual is seeking affiliation. (c) A parent account may be affiliated with multiple minors' accounts. (d) Except as provided by this section, the owner of an app store must obtain consent from the minor's parent or guardian through the parent account affiliated with the minor's account before allowing the minor to: (1) download a software application; (2) purchase a software application; or (3) make a purchase in or using a software application. (e) The owner of an app store must: (1) obtain consent for each individual download or purchase sought by the minor; and (2) notify the developer of each applicable software application if a minor's parent or guardian revokes consent through a parent account. (f) To obtain consent from a minor's parent or guardian under Subsection (d), the owner of an app store may use any reasonable means to: (1) disclose to the parent or guardian: (A) the specific software application or purchase for which consent is sought; (B) the rating under Section 121.052 assigned to the software application or purchase; (C) the specific content or other elements that led to the rating assigned under Section 121.052; (D) the nature of any collection, use, or distribution of personal data that would occur because of the software application or purchase; and (E) any measures taken by the developer of the software application or purchase to protect the personal data of users; (2) give the parent or guardian a clear choice to give or withhold consent for the download or purchase; and (3) ensure that the consent is given: (A) by the parent or guardian; and (B) through the account affiliated with a minor's account under Subsection (a). (g) If a software developer provides the owner of an app store with notice of a change under Section 121.053, the owner of the app store shall: (1) notify any individual who has given consent under this section for a minor's use or purchase relating to a previous version of the changed software application; and (2) obtain consent from the individual for the minor's continued use or purchase of the software application. (h) The owner of an app store is not required to obtain consent from a minor's parent or guardian for: (1) the download of a software application that: (A) provides a user with direct access to emergency services, including: (i) 9-1-1 emergency services; (ii) a crisis hotline; or (iii) an emergency assistance service that is legally available to a minor; (B) limits data collection to information: (i) collected in compliance with the Children's Online Privacy Protection Act of 1998 (15 U.S.C. Section 6501 et seq.); and (ii) necessary for the provision of emergency services; (C) allows a user to access and use the software application without requiring the user to create an account with the software application; and (D) is operated by or in partnership with: (i) a governmental entity; (ii) a nonprofit organization; or (iii) an authorized emergency service provider; or (2) the purchase or download of a software application that is operated by or in partnership with a nonprofit organization that: (A) develops, sponsors, or administers a standardized test used for purposes of admission to or class placement in a postsecondary educational institution or a program within a postsecondary educational institution; and (B) is subject to Subchapter D, Chapter 32, Education Code. Sec. 121.023. DISPLAY OF AGE RATING FOR SOFTWARE APPLICATION. (a) If the owner of an app store that operates in this state has a mechanism for displaying an age rating or other content notice, the owner shall: (1) make available to users an explanation of the mechanism; and (2) display for each software application available for download and purchase on the app store the age rating and other content notice. (b) If the owner of an app store that operates in this state does not have a mechanism for displaying an age rating or other content notice, the owner shall display for each software application available for download and purchase on the app store: (1) the rating under Section 121.052 assigned to the software application; and (2) the specific content or other elements that led to the rating assigned under Section 121.052. (c) The information displayed under this section must be clear, accurate, and conspicuous. Sec. 121.024. INFORMATION FOR SOFTWARE APPLICATION DEVELOPERS. The owner of an app store that operates in this state shall, using a commercially available method, allow the developer of a software application to access current information related to: (1) the age category assigned to each user under Section 121.021(b); and (2) whether consent has been obtained for each minor user under Section 121.022. Sec. 121.025. PROTECTION OF PERSONAL DATA. The owner of an app store that operates in this state shall protect the personal data of users by: (1) limiting the collection and processing of personal data to the minimum amount necessary for: (A) verifying the age of an individual; (B) obtaining consent under Section 121.022; and (C) maintaining compliance records; and (2) transmitting personal data using industry-standard encryption protocols that ensure data integrity and confidentiality. Sec. 121.026. VIOLATION. (a) The owner of an app store that operates in this state violates this subchapter if the owner: (1) enforces a contract or a provision of a terms of service agreement against a minor that the minor entered into or agreed to without consent under Section 121.022; (2) knowingly misrepresents information disclosed under Section 121.022(f)(1); (3) obtains a blanket consent to authorize multiple downloads or purchases; or (4) shares or discloses personal data obtained for purposes of Section 121.021, except as required by Section 121.024 or other law. (b) The owner of an app store is not liable for a violation of Section 121.021 or 121.022 if the owner of the app store: (1) uses widely adopted industry standards to: (A) verify the age of each user as required by Section 121.021; and (B) obtain parental consent as required by Section 121.022; and (2) applies those standards consistently and in good faith. Sec. 121.027. CONSTRUCTION OF SUBCHAPTER. Nothing in this subchapter may be construed to: (1) prevent the owner of an app store that operates in this state from taking reasonable measures to block, detect, or prevent the distribution of: (A) obscene material, as that term is defined by Section 43.21, Penal Code; or (B) other material that may be harmful to minors; (2) require the owner of an app store that operates in this state to disclose a user's personal data to the developer of a software application except as provided by this subchapter; (3) allow the owner of an app store that operates in this state to use a measure required by this chapter in a manner that is arbitrary, capricious, anticompetitive, or unlawful; (4) block or filter spam; (5) prevent criminal activity; or (6) protect the security of an app store or software application. SUBCHAPTER C. DUTIES OF SOFTWARE APPLICATION DEVELOPERS Sec. 121.051. APPLICABILITY OF SUBCHAPTER. This subchapter applies only to the developer of a software application that the developer makes available to users in this state through an app store. Sec. 121.052. DESIGNATION OF AGE RATING. (a) The developer of a software application shall assign to each software application and to each purchase that can be made through the software application an age rating based on the age categories described by Section 121.021(b). (b) The developer of a software application shall provide to each app store through which the developer makes the software application available: (1) each rating assigned under Subsection (a); and (2) the specific content or other elements that led to each rating provided under Subdivision (1). Sec. 121.053. CHANGES TO SOFTWARE APPLICATIONS. (a) The developer of a software application shall provide notice to each app store through which the developer makes the software application available before making any significant change to the terms of service or privacy policy of the software application. (b) For purposes of this section, a change is significant if it: (1) changes the type or category of personal data collected, stored, or shared by the developer; (2) affects or changes the rating assigned to the software application under Section 121.052 or the content or elements that led to that rating; (3) adds new monetization features to the software application, including: (A) new opportunities to make a purchase in or using the software application; or (B) new advertisements in the software application; or (4) materially changes the functionality or user experience of the software application. Sec. 121.054. AGE VERIFICATION. (a) The developer of a software application shall create and implement a system to use information received under Section 121.024 to verify: (1) for each user of the software application, the age category assigned to that user under Section 121.021(b); and (2) for each minor user of the software application, whether consent has been obtained under Section 121.022. (b) The developer of a software application shall use information received from the owner of an app store under Section 121.024 to perform the verification required by this section. Sec. 121.055. USE OF PERSONAL DATA. (a) The developer of a software application may use personal data provided to the developer under Section 121.024 only to: (1) enforce restrictions and protections on the software application related to age; (2) ensure compliance with applicable laws and regulations; and (3) implement safety-related features and default settings. (b) The developer of a software application shall delete personal data provided by the owner of an app store under Section 121.024 on completion of the verification required by Section 121.054. (c) Notwithstanding Subsection (a), nothing in this chapter relieves a social media platform from doing age verification as required by law. Sec. 121.056. VIOLATION. (a) Except as provided by this section, the developer of a software application violates this subchapter if the developer: (1) enforces a contract or a provision of a terms of service agreement against a minor that the minor entered into or agreed to without consent under Section 121.054; (2) knowingly misrepresents an age rating or reason for that rating under Section 121.052; or (3) shares or discloses the personal data of a user that was acquired under this subchapter. (b) The developer of a software application is not liable for a violation of Section 121.052 if the software developer: (1) uses widely adopted industry standards to determine the rating and specific content required by this section; and (2) applies those standards consistently and in good faith. (c) The developer of a software application is not liable for a violation of Section 121.054 if the software developer: (1) relied in good faith on age category and consent information received from the owner of an app store; and (2) otherwise complied with the requirements of this section. SUBCHAPTER D. ENFORCEMENT Sec. 121.101. DECEPTIVE TRADE PRACTICE. A violation of this chapter constitutes a deceptive trade practice in addition to the practices described by Subchapter E, Chapter 17, and is actionable under that subchapter. Sec. 121.102. CUMULATIVE REMEDIES. The remedies provided by this chapter are not exclusive and are in addition to any other action or remedy provided by law. SECTION 2. It is the intent of the legislature that every provision, section, subsection, sentence, clause, phrase, or word in this Act, and every application of the provisions in this Act to every person, group of persons, or circumstances, is severable from each other. If any application of any provision in this Act to any person, group of persons, or circumstances is found by a court to be invalid for any reason, the remaining applications of that provision to all other persons and circumstances shall be severed and may not be affected. SECTION 3. This Act takes effect January 1, 2026.

  ______________________________ 	______________________________
     President of the Senate 	Speaker of the House     

         I hereby certify that S.B. No. 2420 passed the Senate on
  April 16, 2025, by the following vote: Yeas 30, Nays 1; and that
  the Senate concurred in House amendments on May 14, 2025, by the
  following vote: Yeas 30, Nays 1.
  

  ______________________________
  Secretary of the Senate    

         I hereby certify that S.B. No. 2420 passed the House, with
  amendments, on May 9, 2025, by the following vote: Yeas 120,
  Nays 9, three present not voting.
  

  ______________________________
  Chief Clerk of the House   

  

  Approved:
  
  ______________________________ 
              Date
  
  
  ______________________________ 
            Governor
43
 
 
44
45
 
 

Just seen this launcher that's not a fork of launcher3. It's worth keeping an eye on.

46
 
 

PSA: if the installation fails, disable the Desktop experience before the install. If you don't, you'll end up in a bootloop. I'm writing after factory reset... If you turn it off before the install, it will succeed. Otherwise it will roll back. But if you re-enable it after successful update, it will die after every boot. Hence the factory reset, as I didn't have USB debugging enabled and couldn't turn the feature off via ADB.

47
48
49
50
view more: ‹ prev next ›