If anybody cares, the city of Poznań, Poland, has published all their public transit announcements, about 2700 of them, for everybody to Download and enjoy. Cc @Piciokztm.poznan.pl/pl/dla-deweloper…
Great! Now somebody could theoretically build those into a transit schedule app to recreate the announcements system inside our pockets for vehicles where this is missing. I believe Poznań updates their info in real time, actual real time, not every 30 seconds like some cities do so this would actually make sense.
You could always use something like this to track the transit you're waiting for more easily. Would be fun to see how well the message in the app and the vehicle actually arriving would synchronize.
Something like this would have been far more useful here in Wrocław, but our APIs are basically nonexistent. You can get GTFS schedules easily, but that’s about it. Realtime data is available in theory, but it breaks pretty often. If you want to get reliable realtime data or electronic access to the interactive schedule boards that you can find at many bus stops, you essentially have to reverse-engineer the official Android app and connect to the API with its username and password. Of course, none of the boards talk. Buses with no PA system at all, a PA system so quiet that you can barely hear it or a PA system that announces the line but not the stop are also pretty common, especially on some lines.
Yes, I've experienced that. Also, the announcement about the line number and direction being played inside the vehicle only or as soon as it leaves the station. Pretty wild!
Yup. Our vehicles seem to be using the same speaker for the next stop / current stop announcements as for the line/direction announcements. If the line announcement plays with the doors closed, you can barely hear it.
Yesterday I released version 0.4.2 of my XMPP client #Moxxy. This version brings many improvements under the hood and some that are more visible, like a "notes" chat, improved reactions display, and so on.
Gajim 1.8.0 has been released 🥳 and it comes with integrated OMEMO encryption! Integrating the OMEMO plugin brings tighter integration and better user experience.
We also rearranged the chat menu and added some quick buttons for convenience.
Both Gajim’s message search and conversation view received some important changes and fixes.
Gajim 1.8.0 comes with integrated OMEMO encryption! Integrating the OMEMO plugin brings tighter integration and better user experience. We also rearranged the chat menu and added some quick buttons for convenience.
Sort of unrelated but does Gajim do voice/video calling? I looked at it once before and decided against it because it was missing a few features, but I like its interface a little better. If it'll do OMEMO, OpenPGP and voice/video calling it might be time to give it another look, 😊
It’s time to start sharing our video testimonial series! We start off in France with a testimonial from Bachir who has been a proud NVDA user since 2009. Bachir helped translate NVDA into French from 2010 to 2020 & shares how he uses NVDA in his workplace, for online shopping, finances & reading books.
“NVDA is my favourite screen reader… because it makes me independent in daily living.” – Bachir
Thank you for sharing how NVDA has impacted your life Bachir!
We wanted to share some user testimonial videos which have been sent in to us. Here is a testimonial from Bachir in France. Bachir has been a proud NVDA use...
@KaraLG84 Thanks Kara! I'm never quite sure what to put there -you can either specify it as make for kids or not. I thought that just meant it wouldn't necessarily be hidden from people with content restrictions? Or does it come across as only being aimed at kids now?
I don’t know all the details but it turns off a few features such as commenting, ads and things like that. Probably limits them being discovered by the algorithm as well
@KaraLG84 I'll have to look into how that is supposed to work and whether we are support to generally use it or not - I just assumed it was saying "This video doesn't contain any adult or sensitive content, or anything I wouldn't want my 8 year old kid seeing", but I better see what I can find out... Thanks for the prompt!
At work, we recently migrated to MS 365 for part of our email management and I discovered a tiny useful piece of software that simplifies for me the OAUTH2 based idiosyncratic system of Outlook and its friends.
A proxy now allows me to still use mutt, fetchmail, msmtp and exim to read and write emails.
An IMAP/POP/SMTP proxy that transparently adds OAuth 2.0 authentication for email clients that don't support this method. - GitHub - simonrob/email-oauth2-proxy: An IMAP/POP/SMTP proxy that tra...
I've only recommended one VPN service, ever (and no, I don't have any financial relationship to them): Mullvad. They have always seemed to be one of the few entities that practices the mantra, "You don't have to protect what you don't collect."
This is quite a press release:
"Mullvad VPN was subject to a search warrant. Customer data not compromised 20 April 2023 NEWS
On April 18 at least six police officers from the National Operations Department (NOA) of the Swedish Police visited the Mullvad VPN office in Gothenburg with a search warrant. They intended to seize computers with customer data.
In line with our policies such customer data did not exist. We argued they had no reason to expect to find what they were looking for and any seizures would therefore be illegal under Swedish law. After demonstrating that this is indeed how our service works and them consulting the prosecutor they left without taking anything and without any customer information.
If they had taken something that would not have given them access to any customer information.
Mullvad has been operating our VPN service for over 14 years. This is the first time our offices have been visited with a search warrant."
For the past seven years, an online service known as 911 has sold access to hundreds of thousands of Microsoft Windows computers daily, allowing customers to route malicious traffic through PCs in virtually any country or city around the globe…
Good morning everyone. I hope your all having a good day/night. Please remember, your all very much loved and amazing. Always be kind to one another. We need to look out for each other. Today we are gonna be talking about the parsec.
A parsec is a unit of length used to measure vast distances on a cosmic scale. It's an important unit that professional astronomers use to calculate the distance between stars and galaxies, with its definition rooted in the concept of parallax. Essentially, a star located one parsec away from us will appear to shift by precisely one arc-second (1/3600th of a degree when viewed from two different vantage points along the Earth's orbit. By measuring this parallax angle, we can use trigonometry to determine the distance to the star. Parsec is derived from the terms "parallax" and "second", reflecting the scientific principles on which the unit is based.
Wow! As a sci-fi fan I've known the word "parsec" for like the whole my sentient life, but I've never thought about its etimology. Have good day, awesome girl!
Ostatnio na #Mastodon wprowadziło się sporo osób niewidomych. Powodem jest odcięcie przez Twittera dostępu do API co efektywnie unieruchomiło dedykowane nam wygodne nieoficjalne klienty. Teraz szukają tu społeczności, która odpowiadałaby ich zainteresowaniom czy to sportowym, muzycznym czy też Fantasy, Fanfiction itp. Powitajcie ich ciepło i opisujcie obrazki. Nowoprzybyli: dopisujcie się w odpowiedzi pod tym tweetem to będzie Was łatwiej znaleźć. Sami też możecie się przedstawić pod hashtagami na końcu mojego wpisu. Jedna polecajka ode mnie leci dla wszystkich, którzy chcą lepiej poznać #Dostępność Androida. Fantastyczną robotę robi ekipa serwisu @accessibleandroid, dostarczając poradniki, recenzje aplikacji, podcast, forum dyskusyjne, a nawet własną, dedykowaną aplikację, wszystko z myślą o niewidomych użytkownikach robocika. #Introduction #Powitanie
A rzeknij mi, czy te specjalne klienty do Twittera dla niewidomych użytkowników jeszcze działają? TW Blue, Chicken Nugget i co tam jeszcze było. @Piciok @74
@jaczad @74 Padło wszystko oprócz Spring na iOS, czyli poprzednika osławionej Mony. Tweesecake to był ostatni bastion i nawet gdy odcięli mu dostęp na Windowsie, przedłużono mu życie o Święta Wielkanocne za pomocą klucza z wersji na Maca, ale i to padło, dość symbolicznie, bo podczas trwania Tyfloprzeglądu, na którego początku jeszcze słuchacz mówił, że działa.
@jaczad @asael @74 Wszystko przestawia się na Mastodon z perspektywą na inne serwisy o otwartym API. Może inne odnogi Fediversum, a może coś zupełnie innego. Czas pokaże.
@jaczad @asael @74 Mi też się podoba, aczkolwiek, szczerze mówiąc, gdzie indziej mieliby pójść? Chyba żaden inny serwis mikrobloggingowy nie oferuje na tyle elastycznego API. Tu Mastodon był oczywistym i chyba jedynym wyborem.
Są inne oparte o activitypub. Mnie żaden nie przekonał tak, jak Mastodon, ale wybór jest spory. Teraz trochę żałuję, bo może pośpieszyłem się z zamknięciem Tyflodona:) @Piciok @asael @74
@jaczad @asael @74 OK, OK, ale to wszystko jedna rodzina. Miałem raczej na myśli coś zupełnie odklejonego od standardów. Oczywiście mając dostęp do czegokolwiek w Fediversum możemy śledzić używająccccccccccccccccwolnej odnogi.
@ogoniciel @jaczad @asael @74 To zobacz sobie platformy blogowe: Write Freely albo Pleroma to dobre przykłady. Możesz tam pisać cały post, a ludzie z Mastodona będą mogli to śledzić nie musząc tworzyć nowego konta. Ich odpowiedzi na post będą komentarzami pod wpisem na Twoim blogu.
@ogoniciel @jaczad @asael @74 To jest potęga. To bardzo dobrze pokazuje co można uzyskać dzięki otwartoźródłowym rozwiązaniom jeśli są odpowiednio przemyślane. Migracje z Twitterabędą coraz szybciej postępować bo Mastodon otwiera dużo różnych możliwości.
Thanks Paweł, and greetings everyone. Please follow us for everything related to Android and accessibility. Don't hesitate to contact us if you have any questions, whether you're just getting started or have more complex questions. #Introduction
Staying still in the land of open source projects, this slipped yesterday through my Reddit reading: FeedGears is a web-based, self-hostable RSS client with particular attention to accessibility. According to the dev, it was tested against the WCAG 2.1 guidelines on the AA level, has integrated shortcuts, consistent keyboard navigation and automatic announcements for system events. It's pretty new so a lot of features might be missing but that's for the contact mechanisms and the feedback. :) I haven't tested this myself yet but the landing page looks definitely alright. feedgears.com/ #Accessibility #OpenSource #RSS #Blind #ScreenReaders
@pitermach As an RSS buff and as much as I want to use this RSS reader, it fails to analyze my OPML files. Guess it's because my RSS feeds are in a tree view, but other apps like RSSOwlnix can properly import it. On a related topic, Windows 11 has a serious RSS issue as finding capable and accessible clients is a huge pain.
@amirsol @pitermach Agreed. Nothing seems to be living up to Thunderbird's standard and that doesn't do everything that I need, sadly. As for Feed Gears: I guess that's the infancy of the project. I'm sure the dev would be willing to improve the mechanism for OPML import.
@pitermach I use RSSOwlnix on Windows 11, and like it for its wealth of features. However, it gets quite sluggish as time goes by - I mean in a matter of a couple of months, so I'm forced to remove my database, add everything afresh, and re-adjust my settings for yet another couple of months. Really painful to say the least! Wish we had Lire for iOS/Mac on Windows 11.
@gratefuldread Thanks for the heads up. Actually I still need to try it. From what I heard from others it's workable but well-written documentation is a must even for the simplest of solutions. Unless you beat me to it, I'll let the dev know as I doubt he's on here. Have a great day!
The @thunderbird betas have a rewritten main window UI. This has a lot of accessibility problems. Unfortunately, I currently don’t have the energy to file the bugs myself. Here’s what I found:
1. Too many tab stops. Toolbars should definitely be a one-tabstop container and employ the ARIA toolbar design pattern. 2. Speaking of which, the containers should all be made into proper toolbar containers in the process. 3. The main messages list should be a tree with tree items, since they are collapsible. List and list items are not. Also, there are a lot of focus issues still remaining when deleting messages/threads or when the view refreshes from the IMAP server.
Perhaps someone on the team can convert these into proper bugs in Bugzilla, or maybe most of these are already filed. Like I said, I unfortunately currently lack the energy to do so myself.
Me and guy named ali-savas have filed most of these as proper mozilla bugs. Alesandro, Elizabeth and other people on the #Thunderbird team are tackling these as they can. I can already see some of them being addressed in nightlies. Would you like me to post links to individual bugs?
@pvagner Just wanted to jump in and express our appreciation for the work you've done submitting these bugs. We know it takes time and patience to get that done. Thank you!
I have accidentally posted all the issue links twice. Just to add into it here are some recent accessibility related enhancements I have recognized. reporting message columns is now greatly inproved in Thunderbird 114, it is now possible to inwoke the context menu in the message list, dropdown buttons in the message reader UI can now be activated with the enter or space key. F6 and shift+F6 navigation has been improved so it can be inwoked when filter buttons or the edit field has the focus.
Hi Marco, I'm the product design manager at Thunderbird. Thank you so much for trying out beta and for this overview of the issues you encountered. We're 100% aware of all of these and we already have bugs and work in progress patches to address the issues. ARIA toolbar design pattern is currently on alpha (daily) for the message pane, and it will be added to the main toolbar as well in the next months, alongside updating the container markup.
For anyone who hasn't changed their ringtone in a million years or has completely abandoned the idea of those: the Austrian National Forestry department puts up the sounds of all of the beautiful nature that can be encountered within the Austrian forests in the form of mp3 ringtones. Included is everything from common birds to bears and wolves. bundesforste.at/natur-erleben/… #Sound #Ringtone #Nature #Forest #Austria #Mobile #Phones
It's been a while since I've written something for my blog, and just posted about my journey into #TactileGraphics and #TactileArt after having gone #Blind almost a decade ago. I never thought I'd draw again, and here I am helping to teach other blind and low-vision folks how to create drawings both physically and digitally! marconius.com/blog/index.php/2…
Zajímavost: 1. výzkum fotovoltaického jevu se datuje do roku 1839, kdy Edmond Becquerel (otec Henriho Becquerela, objevitele radioaktivity) vytvořil elektrický proud umístěním chloridu stříbrného do kyseliny a jeho vystavením světlu.
Hello @ellieapp, I just found out about the app through HN, and gave it a quick try. I'm blind and use a screen reader (specifically NVDA) and have some suggestions how to improve Ellie's accessibility.
Firstly, most of the controls in the app are currently not labeled. Most critically in the list of posts or notifications, the list items are spoken as just "Ellie.ViewModels.PostListItemViewModel" where I would expect the post content, along with any media descriptions to be read out. Likewise, if you go into the details for a post, all of the various buttons to reply, boost and so on are unlabeled and spoken as just "Button."
The other thing I'd like to mention is keyboard navigation in the app. If I tab to the list of posts or notifications and try pressing down arrow to go to the next post, the app instead brings me into the details for the focused post. Ideally, when the list of posts/notifications is focused the arrow keys should just move through the items, which they do in other parts of the app like the navigation buttons. Speaking of the navigation sections, I can switch to most sections like home, notifications or settings by pressing enter on them, but for some reason if I do it on the compose button the item gets selected but the compose dialog doesn't open unless I do a simulated mouse click on it.
I hope you can look into some of these issues in a future release! :) Ellie has the potential to be a great app for screen reader users - I know several people who want a native Windows Mastodon client.
@colby No worries, and yeah it's just NVDA for the most part. You also have Narrator which is built-into windows but the majority of blind Windows users are on NVDA, and even fore the ones that aren't if you test with NVDA and something works, it should work with other screen readers as well.
+1 to all this. I just tried it as well. I found the same concerns. I'd love to see additional keyboard support for frequent actions such as reply, compose, etc.
@colby Hello again, and thanks for making improvements to Ellie, it's seriously appreciated! The new version is a big improvement, with the labels being much clearer. I have 2 suggestions on how the posts are currently presented, the "post from X" at the beginning of every item is redundant and doesn't need to be there, the label can just start with the author name. It'll make it faster to read through the timeline this way. For boosted posts, there isn't any indication of the original author and I think there should be one. So instead of "boosted post from <booster>", saying something like "<booster> boosted <original author>" would be more helpful.
Also, I'm still seeing some issues with the keyboard navigation. If I tab into the posts lists on any timeline and try to down arrow through the list the app still brings me into the detail view for the first post, and pressing space or enter on the compose button still doesn't bring up the compose screen. I saw mention of keyboard navigation improvements in the changelog which is why I mentioned this again.
While it's very early access, I love the incredibly minimal interface and the snappy responsiveness.
I'm also glad that a new native Windows app was just released because the main Windows app has been Whalebird, and it's much too Slack-like for my liking.
Features are lacking in Ellie right now, such as Federated feed and the ability to upload photos.
In the last 24 hours we became aware of a dump of the Kodi user forum (MyBB) software being advertised for sale on internet forums. This post confirms that a breach has taken place. MyBB admin…
I'm a little worried about supply-chain attacks. It would be a good idea to examine private messages for exchange of credentials. Some add-in developers might have dne that.
NVDA 2023.1 is now available! New paragraph options, link destination & annotated web content keystrokes, new Braille tables, fixes for Kindle, Windows 11, Office, Chrome, Firefox, web, java and more! Read the full what's new & download from: nvaccess.org/post/nvda-2023-1/ Note: This release breaks compatibility with add-ons made for NVDA 2022.4 and earlier. The majority of add-ons have been updated, but please check addons.nvda-project.org/addons… for the status of your favourite add-ons.
NV Access is pleased to announce that version 2023.1 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version. Highlig…
@BTyson According to the user group, NVDA Remote has been updated, but the newer version is currently only on the Spanish add-ons site at: nvda-addons.org/addon.php?id=6…
Welcome to the debut episode of the Thunderbird podcast, which we're affectionately calling the ThunderCast! It's an inside look at the making of Thunderbird, alongside community-driven conversations with our friends in the open-source world.
I'd like to listen it on Google Podcast, but it seems the link is broken (and there is no luck on searching ThunderCast on Google Podcast). Am I seeing a wrong page?
Listen to ThunderCast on Spotify. An inside look at the making of Mozilla Thunderbird, and community-driven conversations with our friends in the open-source software space.
@olikami I can't listen there for whatever reason. Apparently, I have to have an account. Is this correct? can I find it somewhere else, aka tilvids as well?
How cool if Mastodon could (in a Cards-like manner, or perhaps by particular schema.org item handling?) support the data side and enable playing a link to a podcast (or ___) inline?
tabindex is a global attribute that allows an HTML element to receive focus. It needs a value of zero or a negative number in order to work in an accessible way.
Looking forward to presenting on @attie's Show and Tell today at 10 PM UTC (5 PM US Central). I'll spend plenty of time covering modern accessibility, including my AccessKit project. But I'll also be spending some time looking back, including a reconstruction (through emulation) of my very earliest childhood memory of a talking computer. youtube.com/watch?v=1oKeuEZH6E…
Just a heads up that Swamp is now back online. It seems like there are quite a few less players on now days than in the past, so I wanted to make sure everyone knows it’s back. There’s also an event going on currently.
Honestly, that bug is arguably worthy of dunking. I think we might need to get QA testing tagged PDFs more often. I've marked that as a bug with high severity a11y impact, as it could cause people to unsuspectingly break a11y for users reading their PDFs. This is not my team's domain, so I can't promise a quick fix, but I'll do my best to advocate for it.
In about 8 hours there will be a new curl release. In 10 hours there will be a curl release video. There will be blog posts and there will be an online celebration starting in 18 hours.
If you want to say congratulations, share a curl related memory or otherwise celebrate this historic event in text, this is the thread for you. curl was first released on March 20, 1998 when it was...
I've been doing a bunch of performance work in the NVDA screen reader lately to improve responsiveness. A lot of it involves avoiding sleep calls or timers in various places. Among other things, they can be quite inaccurate for short periods < 20 ms. Now I'm seeing that this is even more true when on battery. time.sleep(0.01) in Python seems to sleep for up to 26 ms! This is making me wonder how much this impacts a11y events in Firefox. I've yet to investigate this, but it does seem like a11y focus events are a lot slower on battery, which is pretty suspicious given the above findings.
battery mode often slows down the processor to conserve power, which in turn reduces context switching performance. Dunno what OS this is on, but you may have to install extra modules to get submillisecond accuracy.
@kauer Windows, which is notorious for this kind of thing. There are certainly parts of this we can't avoid - context switching performance reduction, etc. - but I think there's room to improve bits we *can* control - avoiding timers when responsiveness is important, etc.
yes - sleep() in particular is really for giving up the processor not for timing things. "Here, have this spare millisecond" is not usually that useful.
@kauer For sure, but sometimes that's still what we want. There are still times when a timer or a sleep is the right thing to do. All depends on the event in question. For input, we want immediate response. For other events, we want a timer to allow for rate limiting and filtering. Differentiating those events is what this work is about.
Oh I think I've seen this! And when my battery gets below 50% some kind of built-in throttling takes affect which causes all the lag to quadruple. The PC is damn near unusable at that point, I'm probably getting multiple hundreds of milliseconds of delay, as if I were running over Bluetooth audio.
This isn't just firefox either but throughout the entire system. I've tried to disable the throttling but either I'm not looking in the right place or you can't on this machine. It's like the entire core pump is running slower, I've seen it in normally speedy things such as file managers, and even software that uses the NVDA controller client a la invisible interfaces.
@x0 Yeah, some of that we can't fix. Context switching performance is not something we can control, for example. But I think we should be aiming to reduce the bits we can control, which includes avoiding timers for responsiveness hot paths, avoiding unnecessary context switches, avoiding unnecessary mutexes, etc.
Yeah. Given the entire system seems to throttle at that rate I didn't suspect there was all that much you could do, unless I started fiddling with process priority I guess. Should be interesting to see what comes of this work though!
@x0 None of this work has been merged yet, but it'll be interesting to see if it improves things for you. With all of it applied, I notice a significant responsiveness boost even on AC power.
@Nuno It's kinda that, but also a matter of thinking about where rate limiting and filtering are more important vs responsiveness and vice versa. There are still times when a timer or a sleep is the right thing to do. All depends on the event in question. Differentiating those events is what this work is about.
@BTyson NVDA currently queues all events into a core queue and then pumps that queue after 30 ms or less. (It's supposed to be 10 ms, but it isn't in reality due to timer resolution.) There's a good reason for that: it allows NVDA to filter out extraneous/spurious/excessive events, which some apps are unfortunately notorious for sending. However, we want to process keyboard input and focus events as soon as we possibly can, since that impacts how responsive/snappy NVDA feels to the user. So, the first change is that NVDA will force an immediate core queue pump in that case with no timer delay.
I've been thinking about this, and I'm not sure if this is accurate or not but I feel like, for us as blind users, determining how responsive a system is is basically determined by the screen reader and how well it performs. What do you think?
@BTyson It depends. Yes, how responsive things feel is based on how fast the screen reader responds. However, how fast the screen reader responds depends on many factors, many of which are out of the screen reader's control. For example, how fast the system can context switch (switch between processes), how fast the app responds, current CPU load, audio latency, etc. are things we can't control. What this does mean, though, is that we should tune anything we *can* control to within an inch of its life. I think there's been an assumption for a while with NVDA that these things couldn't be tuned much further, but my recent investigations have made it pretty clear that there are definitely still things we can tune for the better here.
@BTyson The second change is that when NVDA re-sends a keyboard command to the OS (e.g. it intercepts an arrow key to speak a character), it previously waited a short while to ensure it didn't get re-captured by NVDA and end up in a feedback loop. It no longer does that, as it doesn't seem to be necessary any more, perhaps because of cleanup elsewhere in the code. The third change is that when trying to detect cursor movement, NVDA now retries a few times without waiting. The retry wait is necessary to reduce CPU usage, but because of timer resolution, that can make things pretty laggy. Retrying a few times without a delay shouldn't have any real impact on CPU, but it does mean we potentially respond a lot faster if the app responds faster than the timer resolution.
@BTyson The new audio backend I'm working on should improve battery life if anything, as it does a lot more stuff in native code, avoids pointless memory copying, eliminates quite a few mutexes, etc.
@bryn @BTyson In reality, it ends up only being about 10 to 20 ms faster, but that is actually pretty significant in terms of audio response feeling "snappier".
@BTyson @bryn Well, we'll see. I don't want to get anyone's hopes up too high; it's still only a tiny improvement in terms of raw numbers. I guess we'll find out once this stuff gets merged... eventually.
Samsung Galaxy phones including those in the S22, M33, M13, M12, A71, A53, A33, A21, A13, A12, and A04 series Vivo phones including those in the S16, S15, S6, X70, X60, and X30 series Google Pixel 6 and 6 Pro, Pixel 6a, Pixel 7 and 7 Pro Any wearables that use the Exynos W920 chipset Any vehicles that use the Exynos Auto T5123 chipset
Project Zero reported 18 vulnerabilities in Exynos modems in late 2022 and early 2023. Four of the vulnerabilities, including CVE-2023-24033, involve internet-to-baseband remote code execution Tests conducted by Project Zero confirm that those four vulnerabilities allow an attacker to remotely compromise a phone at the baseband level with no user interaction, and require only that the attacker know the victim’s phone number. With limited additional research and development, we believe that skilled attackers would be able to quickly create an operational exploit to compromise affected devices silently and remotely.
Project Zero is making a “policy exception to delay disclosure for the four vulnerabilities that allow for internet-to-baseband remote code execution.” This is “due to a very rare combination of level of access these vulnerabilities provide and the speed with which we believe a reliable operational exploit could be crafted.”
FYI, there is an actively funded effort on behalf of the LaTeX Team to make PDF documents created with LaTeX accessible. With only two or three volunteers working in the project it is taking some time, but progress has been made. #TeXLaTeX
First: I know that this has been asked before:
How can tagged PDFs be created that support Universal Accessibility and reflowing? (06/2010)
LaTeX accessibility (05/2011)
Accessibility issues (10/2...
I often use very short microbreaks during the day to doodle away at some music. Let me show you. This is a snippet from the latest thing I've been chipping away at for a couple days here and there. #Music #EDM #MusicProduction #ElectronicMusic
It's not perfect. It's still unfinished, even if it's further along than most of my other projects, so maybe this technique of working on something for a short while agtually works for me. The mix is really hard to get right with so much going on and I had a lot of trouble mixing the low end. I wanted a deep kick but also the bass and they loved to clash in unpleasant ways. Hope it's listenable at least
@Talon Yes an orchestral breakdown, then the main part again and for the radio eed,it that'll be enough. Then make a club mix with beats and the bass line at the begining and at the end so we can mix it on the live gigs. That would be cool.
Didn't know you're into this Trance music. Me and another blind friend from the uk we have a trance project together, and Trance is I think the hardest edm genre to get right when it comes to mixing. I say that from experience.
@djtt88 to be honest I just think it sounds pretty and it kind of ended up that way. I didn't start it with the goal of making a trance track. I just had the melody in mind and it naturally turned out like that. I'm actually pretty unfamiliar with the genre(s) as a whole.
ricardo
in reply to Gajim • • •